• 1 Post
  • 11 Comments
Joined 3 years ago
cake
Cake day: November 27th, 2023

help-circle

  • Not entirely and with absolute certainty, but more than any proprietary software in general. The more eyes on it the better.

    At the end of the day, you have to trust someone and a few black boxes in between as soon as you connect to the internet. So if there’s something I’d really rather not let out into the world, it’s either on an airgapped encrypted system or a piece of paper hidden where my keys get lost.






  • You could make it about equivalent to the protections afforded by the typical BIOS password, i.e. the attacker must first disassemble your laptop to reflash the spi chip or pull the hard drive. A grub.cfg like so would do, assuming everything in encrypted partitions:

    set prefix=(memdisk)/boot/grub
    set superusers="myuser"
    password_pbkdf2 myuser grub.pbkdf2.sha512.10000.<your hashed password>
    cryptomount -u <UUID of LUKS container>
    search.fs_uuid <UUID of the root filesystem under LUKS container> root cryptouuid/<UUID of LUKS container>
    configfile ($root)/@rootfs/boot/grub/grub.cfg
    

    Assuming you boot directly to GRUB or locked out the SeaBIOS boot device selector, then GRUB will only ever look for a boot device matching your disk’s UUID; attempting to do anything else aside from entering the LUKS passphrase will prompt for the GRUB password. You’d still have your own recovery path by pressing Esc, entering your GRUB password, and dropping to the GRUB shell. Bonus points for patching the GRUB code so it doesn’t echo the UUID of your disk.

    No, it isn’t bulletproof against physical access. But yes, I had the same question you did when starting out with coreboot and this was the solution I came up with.


  • Through my entire stint having to use it in Europe, the closest I could find was a webview for the web client: https://f-droid.org/en/packages/io.kuenzler.whatsappwebtogo/

    Sadly, they enforce use of the official client to create an account and resync whenever the web client session expires. Even once got locked out for using the official client downloaded from Aurora Store, apparently I ought to have to downloaded the APK directly from their website, if not from the play store.

    Edit: I also think potential legal pressure also contributes to a FOSS client not existing. Last time someone tried making a feature-complete FOSS Instagram client, they stopped after a cease and desist from Meta.

    Obligatory, I would have loved to go without anything Meta in the first place, but if you’ve spent any time around non-techy colleagues in Europe, you’ll know how much of an uphill battle it is.


  • Focus follows mouse and unchecking the option to auto raise the active window. Couldn’t live without it and being used to it has made me extremely clumsy when I do pick up my Windows work laptop.

    I change the taskbar clock to be a one-line MM/DD HH:MM:SS format, drop in my customized locale (based on en-US for maximum compatibility, but without having to deal with US formats and units that I’m not fond of), and point the taskbar shortcut for my text editor to a script that creates a pre-named file and launches the editor with autosave enabled. Because having to manually save and come up with a name for your spur-of-the-moment notes sucks, automatically generating 20260831_text_1 is so much better than a, b, a2, etc.

    XFCE specific, I get rid of the second panel full of launchers. Acquired taste, but also Chicago95 theme and icon pack.


  • As others say, where the use cases are so specific to each machine, it’ll be a headache juggling all of those images if your needs and workflow change down the road.

    But I’d be remiss to say I don’t practice a form of what you mention, I would go insane if I actually had to reinstall from distro defaults. I have a single perfected VM image with customizations and software common to all of my machines. And yes, if you were to go this route, there are little quirks to iron out manually each time I image to a new machine, even old and well-supported ones. Some just cosmetic, some preventing graphical output. Although still much less time than setting up from scratch.

    It works well enough for me, but it also frankly leads to a poorly-documented system that will accumulate cruft with updates, and can’t propagate changes in the VM to my existing systems easily, so I’m interested too to see what other people here suggest. Particularly for those niche customizations that land outside of /home and /etc (e.g. /usr/fonts, packages not provided by the distro).