• 30 Posts
  • 269 Comments
Joined 2 years ago
cake
Cake day: November 27th, 2023

help-circle






  • If you don’t want Ventoy:

    1. Wipe the USB: wipefs -a /dev/sdb
    2. Copy the ISO image to the USB: dd of=/dev/sdb if=/path/to/image/linux.ISO bs=1M status=progress
    3. Make the data partition in the free space: cfdisk /dev/sdb, don’t remove the iso9660 signature, create partition in the free space, and Write.
    4. Format the partition with filesystem of your choice: mkfs, cryptsetup, etc.

    (everything as root, replace /dev/sdb with the location of your USB)

    As is, this only leaves exactly enough for the ISO you are currently working with, sealing the fate of the data partition if you need to swap out the ISO. I suspect there is a workaround in theory, but I haven’t gotten around to that yet.

    Also see https://github.com/thias/glim, a GRUB-based alternative to Ventoy, albeit with less compatibility.

    Edit: this will not work with Windows ISOs and the data partition won’t show up in certain versions of Windows, in case anyone is wondering

    For posterity, what I originally thought, don't do this

    Wipe the drive and partition it so the first partition is large enough for your ISO, then the second partition for your data spans the remaining space. I chose MBR over GPT so I could boot on both modern and legacy BIOS machines. Then dd your ISO to the first partition. Set the bootable flag on that partition if it isn’t already. Format the second partition with whatever filesystem you’d like.

    My Clonezilla recovery drive is set up like this, but it’s been a while so I might have forgotten something. Let me know if I did.



  • As someone who did use this guide as an exercise in making my setup as secure as it could be without changing distros or hampering productivity, a few words of advice:

    • Make a threat model for yourself before diving in and apply the mitigations judiciously. It’s not exactly a checklist, just use something secureblue or Qubes if you are really paranoid about your computer.
    • The majority of the mitigations ‘just work’ and have no noticeable impact on performance, battery life, or compatibility.
    • If your CPU/Memory performance widget breaks, dial back on the ptrace options
    • If Flatpaks fail to launch, dial back on the namespace options
    • Check back every so often because some of the options end up having unwanted side-effects with updates. See the preamble in boot parameters, where a change in Linux made in 2021 (which finally made it into Debian Stable this year) made the slub_debug mitigation actually worsen security.



  • Lenovo’s ThinkPad line has a sterling reputation. Among the best in terms of quality, service, repairability, and Linux support.

    As for the largely consumer-grade options of ASUS and Lenovo’s consumer-grade IdeaPads, they’re rather similar in reputation and quality. Not exceptional, but they’re both perfectly fine options as long as you avoid the budget laptop segment (plastic chassis, broken hinges, etc.)

    Any difference in privacy would come down to the pre-installed software, which is irrelevant if you plan on using Linux. If you will be using Windows, it’s always better to install your own fresh copy to purge any potential spyware and bloatware installed by the manufacturer. The activation key for whichever edition of Windows it comes with is embedded in the BIOS, so it’ll activate automatically after a fresh reinstall.




  • It’s there to protect you from crimes of opportunity. Like if your car is locked, a thief could decide to pick the lock, smash the windows in, or find another victim, but they would have no second thoughts if your car were already unlocked. The password deters a casual hacker and buys you some time to notice and deal with anyone seriously trying to break in.

    In an ideal case of disk encryption and a well-designed lock screen, the password forces a would-be intruder to either spend lots of time guessing it or shut down the computer, thereby discarding the encryption key from memory and thwarting the attack.







  • I daily drive Debian now, but several years ago when a couple of my computers were still very new, I used Arch since it has bleeding-edge support for new hardware while being still thoroughly documented in the Arch Wiki.

    The sheer volume of packages on the official repo and the AUR made it great for discovering which desktop environment I wanted to use and for software-hopping in general too. You can have as much or as little on your system as you want and nothing is forced on you.