Earlier quoted context omitted.
Stored encrypted of course with a long password...
My response was in regard to the bitrot argument.
So I lost my OpenBSD FDE password (2016)
71–77 of 77 posts
Re: So I lost my OpenBSD FDE password (2016)
#72I’ve just been using the same password for my FDE forever, and only for that purpose. I figure it keeps my data safe from theft, but probably not from the feds or my wife if she wanted in there, because they could either compel me to unlock it or have access to put some keyboard sniffer in my boot loader. The password is quite a few random characters that I memorized when I first used FDE decades ago and I’ve never h…
battery horse stapler in a playfair grid? https://en.wikipedia.org/wiki/Playfair_cipher Not the full cypher but just reading out the letters in the grid in a different direction.
Re: So I lost my OpenBSD FDE password (2016)
#73Earlier quoted context omitted.
Your mother wouldn’t benefit from backups? The idea here is that you get backups working first, because data loss is the most serious risk, and then you later consider whether you want full disk encryption once you have backups working. Encryption is designed to make data difficult to access, so it makes sense to consider backups and encryption jointly. I don’t understand why someone would consider this controversial…
Now you need to manage password to your backups (that you would encrypt, else why bother with encryption in the first place?) and to your encryption. Or maybe just capitulate and admit that a bunch of kids, people and cat pictures maybe don't need to sit on encrypted storage
You seem to be arguing against something here, but it sounds like it’s really just a miscommunication. The original prompt was to fit the instructions on a postcard, and and perhaps it’s not really possible to fit good instructions on a postcard.
In order to fit instructions on a postcard, there are a number of things I left out with the idea that someone could figure them out. Stuff like “how do I do backups” or “should I encrypt my backups”. I thought that people could figure out to encrypt their backups if they wanted to, because backup solutions have that option. I also thought that people could figure out that you’d also encrypt your backups if you encrypted your hard drive. Maybe I should have spelled it out in excruciating detail.
As far as I can tell, that’s the lesson here—spell things out in excruciating detail, or you’ll get sarcastic jabs in the replies.
Re: So I lost my OpenBSD FDE password (2016)
#74Re: So I lost my OpenBSD FDE password (2016)
#75Earlier quoted context omitted.
My response was in regard to the bitrot argument.
Backing up software isn't going to help against it bitrotting away.
Re: So I lost my OpenBSD FDE password (2016)
#76Earlier quoted context omitted.
As much as I adore my Yuibikey, my girlfriend thinks I’m decidedly weird because I have two: one on my actual keys, and a backup that’s in my safe at home. Which is annoying because not every system lets me setup two Yubikeys (though TOTP is fine at least). I’m not using it for FDE, but I am using it for securing my password manager (which does support both keys) which holds the backup keys for said FDE and so on.
The issue I have is that the second key can't really sit in the safe all the time because everytime you setup new service, it needs to be taken out and added.
Re: So I lost my OpenBSD FDE password (2016)
#77I've been meaning to do this with my LUKS headers and zpool headers since reading about fast bcrypts via GPU a few weeks ago; I suspect that my FDE passwords are not powerful enough, but I'd like to put them to the test.
just add aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa in front of it so bruteforcing will not try anything with enough characters to even get close to your password (/s)