WireGuard protocol logs very little information by default. There is literally no way to make it log more than it does by default.
Even then, Mullvad has no customer information. You’re given a customer number, which is intentional.
I stand by my initial post in that there is very little, if anything, to record on a Mullvad server. If I’m not mistaken, Mullvad recently announced they are running all VPN services through a RAM only setup, therefore, there aren’t even any drives to record customer information even if they chose to.
There absolutely is a way to make it log more. Simply add a function to dump the data passing through it. Just because right now there is no such function does not mean one cannot be added.
Sure, add it, but good luck logging in a RAM only setup. We’re talking semantics because frankly, it doesn’t currently affect Mullvad. If it does, we’ll have to worry about it then.
WireGuard protocol logs very little information by default. There is literally no way to make it log more than it does by default.
Even then, Mullvad has no customer information. You’re given a customer number, which is intentional.
I stand by my initial post in that there is very little, if anything, to record on a Mullvad server. If I’m not mistaken, Mullvad recently announced they are running all VPN services through a RAM only setup, therefore, there aren’t even any drives to record customer information even if they chose to.
There absolutely is a way to make it log more. Simply add a function to dump the data passing through it. Just because right now there is no such function does not mean one cannot be added.
Sure, add it, but good luck logging in a RAM only setup. We’re talking semantics because frankly, it doesn’t currently affect Mullvad. If it does, we’ll have to worry about it then.