I'm pretty sure all the major distros have FDE as an option in the installer its just never on by default. Fedora does the same but with BTRFS on LUKS. I'm sure Debian does. Someone else says OpenSuse does. Maybe some derivative distros don't but I suspect the ones with an graphical installer do.
sudo
Looks like they use eCryptFS. Never heard of it before so thats neat. I can see using it on systems where you can't reinstall the system with Dm-crypt but it most cases I suspect Dm-crypt is a better alternative.
Idk if its faster or slower than Dm-crypt.
The standard route is to decrypt on boot. It happens after GRUB but before your display manager starts. IDK if there even is a setup that has you "decrypt on login". Thats sounds like your display manager (sddm for KDE) is decrypting system which is not possible IMO.
Unless your laptop somehow has multiple drives you'll want to use the "LVM on LUKS" configuration. 1 small partition for /boot
. The rest gets LUKS encrypted, and an LVM group is put on the LUKS container. Or you could replace LVM with btrfs.
This will require wiping your system and reinstalling so you have some reading to do.
- https://wiki.archlinux.org/title/Dm-crypt (aka LUKS)
- https://wiki.archlinux.org/title/Dm-crypt/System_configuration
- https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system
- https://wiki.archlinux.org/title/Dm-crypt/Encrypting_an_entire_system#LVM_on_LUKS
The arch-install
script in the live iso has options for full disk encryption.
If you suspend to RAM your system will stay unencrypted, because your ram is not encrypted. if you suspend to disk (aka hibernate) your system will be encrypted. You go through the boot loader when waking from hibernation but it just drops you off where you left off.
You need a swapfile for hibernation so make sure its inside the LUKS container.
Unironically try turning your computer off and on again.
Tmux settings are global and persistent. Just deleting your config files is insufficient. You have to kill the server and restart it. Uninstalling and reinstalling will not kill a running tmux server. tmux kill-server
should work too.
Now if it persists across reboots, then there must be a file still lingering somewhere. If you are sure your home directory is clean you can try searching whatever you installed in /etc.
This is all assuming you're trying to go back to a clean slate and failing. If the borked status bar is the result of your current .tmux.conf
, then you'll have to post that.
I spent like a week on this last month. Usually you use enumeration, but I wanted to allow client code to define their own strategies. I tried the Box<dyn MyTrait>
pattern because some of my strategies were composed of other strategies, and I wanted to clamp down on generic types. But I kept running into weirder and weirder compiler errors. Always asking for an additional restriction on the base trait. X, must be Copy
, must be Send
, must be Sized
, must be 'static
. On and on. My experience is if I'm getting a bunch of those then I'm off the Golden Path. So I just embraced the verbosity of using generics and its easy. Yes its more code but its better code.
Its going installed binary is rg
.
Irrelevant to the point I'm making. We, the US, are the ones starving Venezuelans, not Maduro. Everything else is none of our business.
… but it’s the US imperialism that’s at fault, obviously
It's literally the direct consequence of US sanctions. That's the literal goal of sanctions.
Holy fuck the Gravel Institute is a nostalgia trip. Can't believe those kids still have a job.
Who actually hates on declarative/immutable distros as a concept? Its always the actual usability of the specific implementations thats the problem. Stale packages, poor documentation.
I knew Palestine was British at the time I just never heard that the British elites portrayed as evangelicals before. I always clocked them racist imperialists, not zealots trying to bring about the apocalypse.
Also calm the fuck down. I'm not sealioning. I'm legitimately curious. You're more than welcome to go through my comment history to see I've taken a clear stance on Palestinian liberation.
I think PopOS can safely assume that its being installed on a laptop with only one drive. If there's multiple drives involved then the setup gets far more complicated as you then must go to something like an LUKS on LVM setup. Basically, for a desktop there's no safe defaults for FDE.