Richard Stallman, the man behind GNU and FSF. He makes a distinction between free software and open source software.
Stallman is not a pragmatist. He quit his job as a professor at MIT because he felt they were forcing him to use proprietary software, which contradicted his ideals.
Linus still keeps Linux on GPLv2 because he disagrees with GPLv3+ and its anti-tivotization clauses. Companies that contribute code back to Linux is good enough for him. Linus has a more pragmatic view.
FSF and OSI have slightly different definitions for software. FSF believes in free and open source software (copyleft i.e. GPL) whereas OSI believes in permissive, open source licenses (i.e. MIT/BSD).
In the 1990s, they had disagreements against each other because FSF and Stallman believe in FLOSS/FOSS and free software advocacy politics. OSI was more concerned with open source workflows and not with free software advocacy politics, which was initially more popular with businesses.
The Ubuntu based distros may have this phased update thing. That AskUbuntu link has a command to override APT package manager to install the held-back packages.
Ubuntu tends to hold back system critical packages in case there are issues. Systems with certain install UUIDs will be ‘guinea pigs’ and install these packages before everyone else. You can override this behavior and disable phased updates on that particular computer.
Are you talking about addresses like 192.168.x.x? Do you have subnet routing enabled in Tailscale?
That just means the TPM will not auto unlock the encrypted disk. You would have to unlock with whatever LUKS password (or key file) you set for that drive. There is optionally a TPM master key you can export that is similar to the Microsoft Bitlocker password (40 digit number iirc), that Lennart mentioned in his blog. If you deleted any other key slots and do not have that TPM master key, you will not be able to unlock the LUKS drive.
If you look at that freedesktop manpage I linked, it states some of the PCR values and what each one measures. When you enroll a PCR, that value is stored in the TPM. If anything differs between the system and the TPM, the TPM will refuse to unlock that encrypted drive.
For example, PCR 0 measures your motherboard UEFI firmware. If you update the firmware, the TPM will not unlock your LUKS drive until you re-enroll the drive once again. Is is a personal choice, but enrolling certain PCR into the TPM can be more inconvenient.
I think pcr 7+8 (for grub) or pcr 7+12 (for systemd-boot) should be okay. The more pcr you add, the higher likelihood you need to re-enroll after updates.
https://www.freedesktop.org/software/systemd/man/systemd-cryptenroll.html
The reason why using your own keys can be a problem is if you exclude the Microsoft certificates, then oproms from graphics cards stop working. You have to add the Microsoft certs after using your own key for the top level platform key.
For Debian, if you use out of kernel modules like Nvidia, you have create signing keys and edit a config file so dkms to sign those modules for those modules to work with Secure Boot. Instructions are on the Debian wiki.
Hyprland dev’s response to blog post: https://blog.vaxry.net/articles/2023-hyprlandsCommunity