I never use full disk encryption. I can understand the use case for a laptop. But I know that the person most likely to get locked out of my data is me.
The final straw before I switched to Linux was when M$ turned on bitlocker without my knowledge. I didn’t find out until I did something in the UEFI that made my disk button up and lock me out. I was able to easily recover my data, but that was because M$ stored a copy of my key. Which defeats half the point of encryption in the first place.
I agree on that for most people, but for good opsec, then full disk encryption will (most likely) prevent law enforcement from hacking into it by themselves if you were unable to nuke everything before they got to it. So it’s useful if say you have evidence saved that Putin is a lolicon but you live in Russia or something
Microsoft most likely provides law enforcement with backdoors. Even if not, the software run before unlock is so flawed there will be many products for sale to law enforcement by 3rd parties that allow circumvention.
Every few years for example there is another accessibility tool ms is discovered to have forgotten to lock down, that lets you go to its file dropdown and access the filesystem before logging in (this literally happened again today).
And then yellowkey would likely be someone finding a backdoor.Technically the chance it stops some state isn’t 0, but at some point the value is negative. Just you thinking yourself secure and not taking other measures or risking more makes it decidedly not worth it in this case I would say.
Also this costs performance, and gives a risk of being locked out. There are cased were ms accounts are hacked, bitlocker remotely engaged and the keys then locally corrupted, and then the recovery from the ms account taken and deleted and then ransomed back to you. Basically using just the ms account to remotely ransomware your pc.You’re better off taking the performance cost to something proper and layering something around the OS where you do the encryption. Then setting a password on that, or just decrypting with password, and then booting into the bad os without further login.
I mean, I was more so referring to Linux full disk encryption so there would hopefully be no government mandated backdoor, should have made that more clear though. You make a great point about the tradeoffs though, which is why I wouldn’t recommend it for most people
Yeah for me it also just depends on the context. I do use full disk encryption on my laptop and some of my portable drives where I may accidentally leave it somewhere. But on my desktop internal drives I don’t bother. I’m not exactly a high profile target with a bunch of secrets and someone who does burglaries is just going to try and pawn it or whatever and any place that buys used tech these days wipes drives. And burglary is just a very rare crime anyway. I do a lot for privacy and security but its usually best to weigh the hassle against the risk.
I wouldn’t trust thieves to just be wiping drives Immediately… in fact I wouldn’t be surprised if there was a guy specifically buying unwiped drivee
If the previous install was already fully encrypted you don’t have to wait. The disk is already just random nonsense. Just skip this step.
When Debian mentioned nothing about previous encryption, I thought every time erasing data was essential.
Btw, Fedora only took the same installation time even if encryption was ticked or not.
Yeah, that’s the purpose of full encryption. I don’t see the problem.
There is no problem at all. Just more time to touch the grass actually.
Can’t you just untick the “Erase disk” option?
Personally, I’ve only ever used it accidentally. Just do a blkdiscard before installing (anyway) and that’s it.
It takes way to long on flash memory. What is it doing? It should rewite every block on a HDD, but on flash, a full erase should take seconds. I hope it’s not doing the same thing on flash memory.
I hope it’s not doing the same thing on flash memory.
You can of course decide that the extra step in unneccessary, but it’s not like the affitional 1-3 read/write accesses really hurt
I guess not, but depending on the size and TBW of the drive (say you get an older, used model), wouldn’t wanna waste any more writes on this, especially since it would be useless.
hdparm security-erasedrops all keys instantly and marks every cell as free, it’s basically doing the same thing without the additional writes.
Partially same as @yesman@lemmy.world . I used to encrypt both the system, internal storage and removable storage - all with different 35+ char passwords - until I learned how to threat model. Now I only do system encryption on my Laptop and encrypt internal and removable storage only. In the astronomically unlikely event the feds kick down my door for downloading Linux ISOs, I just hit the power button on my rig and the drives are scrambled. As a bonus, my
HISTFILEs areunsetso history is lost at every logout or any other session restart. Oh, and.bash_logoutis set to do ahistory -c, just in case.my
HISTFILEs areunsetso history is lost at every logout or any other session restart. Oh, and.bash_logoutis set to do ahistory -c, just in caseThis guy doesn’t like
^rNot across sessions, no :D
Do you have dotfiles for that somewhere on the internet?
What’s a dotfile? 🫣
Edit: I see. I don’t. Open your
.bashrc(or/etc/profileif you want the settings to apply to all users) with your favorite text editor and addunset HISTFILEto disable automatic saving of command history. Similarly, addhistory -cto.bash_logout(or to/etc/bash.bash_logoutfor system wide). Reboot or logout/login orsourcethe above files to apply immediately.A dotfile is your next rabbit hole!
You know that dotfiles (files that begin with a dot) like
.zshrcor.bash_logoutcan contain important scripts or configuration for your system(s). Same with all the configuration files that can be scattered in directories like.config/or.gnome/.The “modern” dotfile means a configuration file that has been saved somewhere so that you can make a backup, or have the same dotfiles on all your machines.
It’s usually saved in git and on GitHub, but crazy people have written whole applications to handle those files (https://wiki.archlinux.org/title/Dotfiles#Tools). I like chezmoi, written in Go, but you have others like
stowfor example. Those applications handle diffs (when a file has been changed, you see the diff, you can save it or reset it), templates, multiple machines, upload to git, etc. Some applications use a hidden git repository for your files, others use hard-links. Last but not least, you can say “here are the files for Windows, and others files for Linux” if you have different machines.At my last job I stored on GitLab all the ZSH configuration files, CLI applications configuration, and even macOS configuration files that were in my HOME directory. If my machine ever crashed, I would have been able to restore it in a few minutes thanks to chezmoi, like: format computer, install chezmoi and git, reapply all the dotfiles as if nothing happened.
If you want examples of what can be done, a lot of people store theirs on GitHub: https://github.com/search?q=dotfiles&type=repositories
And this: https://github.com/webpro/awesome-dotfilesJesus Christ 😅 I knew what they are, then, without knowing what they’re called. But what on earth is all this managing enthusiasm surrounding them?! 😅 Would one have a 100 versions of the same dotfile or what? Mind you I have three computers, manually manage a handful of dotfiles + having a backup of them. Please explain a scenario where I would need one of those honking management tools. 🥹
Practice, paranoia, obsession.
dealer’s choice
But what on earth is all this managing enthusiasm surrounding them
It looks like a fad, but when you use it once you can be hooked. I see this see as an additional step in automation and making sure your computer is properly set up.
Having the same files across all machines is nice, and it’s backed up. You don’t have to think about it every day, at most once a week to check if a file has been changed and not pushed to git.
Most of the time, you want to have the same .zshrc across all Linuxes and Macs. That’s where such a tool can be useful.
Would one have a 100 versions of the same dotfile or what
If it’s in a git repository, the latest commit (transparent if you use a tool) has your files. At most 20 unique files for me but all at the latest “git version.”
Please explain a scenario where I would need one of those honking management tools
If you want to save your dotfiles on git, or if you want to have the same configuration on multiple Linux machines.
I don’t remember the commands but once a week I would do:
chezmoi diff # to check if a dotfile has not been backed up chezmoi add ... # to add new or modified files chezmoi git push # to save my modifications
deleted by creator
Did it actually erase the data or did it do the smarter thing of erasing the key twice?
I think OP is talking about the installation step where it’s filling the entire partition (overwriting anything that could have been sitting there cleartext).








