this post was submitted on 20 Sep 2023
822 points (98.8% liked)

Privacy

31833 readers
131 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

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

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
[–] csolisr@communities.azkware.net 24 points 1 year ago (15 children)

From what I read in the article, there is still one part of the boot sequence that does require some sort of storage: the part where the bootloader fetches the network boot image and verifies it against the checksum signature. But I think that can be performed by booting from a pendrive and then removing it. The problem will come if law enforcement gets a hold of said pendrive...

[–] ikidd@lemmy.world 25 points 1 year ago (8 children)

PXE boot will TFTP the boot image into RAM and carry on from there. You shouldn't need any storage on your device.

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

I'm aware of PXE, but in order to do so you need either of:

  • the boot image supplying server being in the same intranet as the rest of the other servers, or
  • some sort of method to point the diskless server to the correct external IP address to listen to

Since the first mode is probably too unsafe, that leaves us with the second mode. Either the operator memorizes a specific IP address and types it into the BIOS each time the server is rebooted, or the IP address (and possibly the checksum of the image) are stored in a single-use pendrive that the operator carries. I wonder which of these two methods is used in this case.

[–] 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)
[–] 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?

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)

load more comments (5 replies)
load more comments (5 replies)
load more comments (11 replies)