this post was submitted on 27 Nov 2023
22 points (95.8% liked)

Privacy

31957 readers
491 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
 

cross-posted from: https://lemmy.cat/post/6027277

I'm curious to know how people manage their different encrypted storage here. And I'm talking about the case where you really need to manage SEVERAL encrypted storages/files.

What software do you use? Where do you save your passwords (password manager/paper/other) or do you use physical keys?

In short, what's the best combination you've found or recommend to cover as many attack surfaces as possible: remote, local, physical, etc.?

top 7 comments
sorted by: hot top controversial new old
[–] [email protected] 8 points 11 months ago (3 children)

Linux and Luks full-disk-encryption for every system. Remotely unlockable via ssh. HDDs are unlocked via keyfiles which are on the fd-encrypted SSDs.

For windows you can use VeraCrypt (don't use Bitlocker!).

For single files I usually use 7zip or Peazip with long passwords.

[–] [email protected] 3 points 11 months ago

HDDs are unlocked via keyfiles which are on the fd-encrypted SSDs

I hadn't even thought of that!

[–] [email protected] 1 points 11 months ago* (last edited 11 months ago) (1 children)
[–] [email protected] 2 points 11 months ago (1 children)

Why riskier? Keep a backup of the boot-image and you're good. And do generally backups of files and devices. Haven't had any issue for years with Win10/11 and VC. Win7 and TC/VC on the other hand was awful...

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

I like this idea. I never use keyfiles - I'm irrationally paranoid of losing them - but I've been doing a good job of regularly backing up (in a way I'm confident of recovering from) for the past several years, so I'm going to let go of that fear and embrace keyfiles.

[–] [email protected] 7 points 11 months ago

gocryptfs, because encrypted shares are accessible cross-platform(ish), and I have high confidence of having either a working static binary, or the ability to compile one, several years in the future.

Passwords are all in a pass store, and also in a keepass db. I'm probably going to do away with pass and go back to some secret-tool backed be keepassxc, though, as I haven't been very happy with pass (I use gopass, but same db format). I depend far more on keepass, and keeping the dbs in sync is a minor PITA, as well.

In any case, I have a bespoke bash script that mounts/unmounts shares on demand via a rofi dialog. pgp-agent does the password prompting as necessary, which pass uses to decrypt the passwords.

Everything - including the encrypted shares - is backed up by restic to encrypted backups - one each in B2, one each on local portable USB HDs.