Privacy

32120 readers

396 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
Don't promote proprietary software
Try to keep things on topic
If you have a question, please try searching for previous discussions, maybe it has already been answered
Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
Be nice :)

Related communities

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago

MODERATORS

911

Mullvad Annouce Removal Of All Disk Infrastructure - Now RAM Only (mullvad.net)

submitted 1 year ago by leraje@lemmy.blahaj.zone to c/privacy@lemmy.ml

129 comments fedilink hide all child comments

Today we announce that we have completely removed all traces of disks being used by our VPN infrastructure!

you are viewing a single comment's thread
view the rest of the comments

[–] sixCats@lemmy.dbzer0.com 3 points 1 year ago (1 children)

I’ve never done this, but I believe server network cards can be configured for PXE automatically so

Bios -> network card -> PXE over network

So the storage is in the bios config, and then I guess the network card has its own kind of bios?

[–] csolisr@communities.azkware.net -1 points 1 year ago (1 children)

So there is still one single damning piece of information stored in the servers after all - the IP address to fetch the PXE boot image from. But hey, if Mullvad finds a way to strip even that out of the servers, that'd be great

[–] sixCats@lemmy.dbzer0.com 2 points 1 year ago (1 children)

Why is it damning?

[–] csolisr@communities.azkware.net 0 points 1 year ago (1 children)

Because by knowing which IP is the boot image stored from, law enforcement can locate the source of the unencrypted image, thus making the scheme lose its privacy. The only way to bypass the issue is by manually configuring the IP after every reboot and keeping it a secret.

[–] sixCats@lemmy.dbzer0.com 2 points 1 year ago (1 children)

Why does being able to access the unencrypted image pose such a problem?

[–] csolisr@communities.azkware.net 1 points 1 year ago

Because by doing so, law enforcement can manipulate the image from the source by:

Intercepting the payload and modifying the operative system to send data to law enforcement
Pose as the origin of the original payload, and send the tainted operative system to other devices when they reboot

Unless, of course, the BIOS stores the checksum of the untainted image. (Which adds its own can of worms, because that would make legitimate image upgrades require writing the new proper checksum on each server)