Proton

5270 readers

1 users here now

Empowering you to choose a better internet where privacy is the default. Protect yourself online with Proton Mail, Proton VPN, Proton Calendar, Proton Drive. Proton Pass and SimpleLogin.

Proton Mail is the world's largest secure email provider. Swiss, end-to-end encrypted, private, and free.

Proton VPN is the world’s only open-source, publicly audited, unlimited and free VPN. Swiss-based, no-ads, and no-logs.

Proton Calendar is the world's first end-to-end encrypted calendar that allows you to keep your life private.

Proton Drive is a free end-to-end encrypted cloud storage that allows you to securely backup and share your files. It's open source, publicly audited, and Swiss-based.

Proton Pass Proton Pass is a free and open-source password manager which brings a higher level of security with rigorous end-to-end encryption of all data (including usernames, URLs, notes, and more) and email alias support.

SimpleLogin lets you send and receive emails anonymously via easily-generated unique email aliases.

founded 1 year ago

MODERATORS

[email protected]

Why Proton VPN doesn’t use RAM-only VPN servers | Proton (protonvpn.com)

submitted 3 months ago by [email protected] to c/[email protected]

3 comments fedilink hide all child comments

Proton VPN doesn't use RAM-only servers, arguing they offer no additional security over full-disk encryption on hard drives.
Full-disk encryption ensures data on hard drives is secure and inaccessible without proper authentication, even when servers are powered off.
Proton VPN prioritizes a strict no-logs policy, independent audits, and operating servers in privacy-friendly jurisdictions to protect user privacy.

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

[–] [email protected] 0 points 3 months ago* (last edited 3 months ago)

While I'm not particularly invested in their choice, I will say that I've got some counters to the points given as to why not:

Logging for diagnostics: probably the closest point, but you can either centralize such logs where local disk does not matter, or leave log in ram with aggressive rotation out.
Ability to update without rebooting. The diskless systems I work with can be updated live too. However live updates do eat more memory in my case due to reasons that will be clear soon. Besides, a rolling reboot should be fairly non disruptive to "bake" the live updates into the efficient form. Other Diskless situations just live in tmpfs, in which case live updates are no problem at all, though it is a lot of ram to do this.
Diskless uses too much RAM: At least with the setups I work with, the Diskless ram usage is small, as the root filesystem is downloaded on demand with a write overlay in zram to compress all writes. Effectively like a livecd generally boots, but replace cd with a network filesystem.