Linux - Reddit – Telegram
Linux - Reddit
763 subscribers
4.19K photos
207 videos
39.9K links
Stay up-to-date with everything Linux!
Content directly fetched from the subreddit just for you.

Powered by : @r_channels
Download Telegram
What would it take for Linux to support TPM-backed biometric keyring unlocks?

After using Linux for the better part of a decade, I've recently had to start using Windows for work - and one of the things that I've gotten used to really quickly is using my face to log in with Windows Hello.


I found a cool solution for this on Linux called Howdy, which lets you log in with your face in the same way. It works really well, but the annoying part is that Gnome keyring doesn't unlock, so I have to type in my password anyway after reboot.


I believe the problem here is that the key used to encrypt and decrypt the keyring is derived from your password, which means biometrics through Howdy or fprintd won't work to unlock it.


Does anyone know if there is any work being done on supporting biometrics for decrypting a keyring? My understanding is that Windows has this set up by generating a random encryption key and storing it in some secure enclave backed by the TPM module. And then setting it up so password, pin, fingerprint, face, etc. can all unlock the secure enclave to retrieve the key for decryption (someone please correct me if I'm wrong here).

A lot of modern laptops have TPM now. I know it's also possible to use TPM to, for example, automatically decrypt a LUKS partition. And Linux already has good biometric auth support. Is it possible that we ever see biometric unlocking of TPM secrets in the near future? Is there any ongoing work on this?

I'd love to work on this, but it seems like such a feature would require changes in PAM, fprintd, Howdy, keyring, and maybe more.

https://redd.it/1qzo6yc
@r_linux
Linux gets exposure in OpenAI Super Bowl TV Ad

https://www.youtube.com/watch?v=aCN9iCXNJqQ

You can see a generic Linux CD/DVD inserted in an old PC at the 0:19 mark of the video. Any visibility for Linux is good I guess.

https://redd.it/1qzpnjs
@r_linux
What is your preferred software installation method?

For me, I always install software from the main repo first before going to anywhere else.

If it doesn't exist on the main repo, I install it from flatpak.

If it doesn't exist on flatpak, I extract the .tar.gz from github to /opt/software_name folder and use a symlink to /usr/local/bin/software_name so I can run it from anywhere. I rather avoid installing "universal" .deb file or "noscripts" because of the risk of "FrankenDebian".

If it a "24/7" software that always runs on the background like pihole, arr-stack, plex, etc, I installed it on a Docker container.

Which method do you guys often use?

https://redd.it/1qzvqd7
@r_linux
Sydney metro screens running ubuntu
https://redd.it/1qzytik
@r_linux
os-prober not finding Windows Boot Manager

Since I couldn't find this solution anywhere on the internet, I want to share my solution, hoping it could be useful for someone else.

# Context

I have a dual boot with Ubuntu + Windows 11 on my laptop, the first installation was done two years ago on two separate 512GB SSDs with two separate EFI partitions, then on Ubuntu I added the Windows entry to GRUB with os-prober.
Everything worked fine until I replaced the two SSDs with a single 1TB one holding both OSes, I copied the EFI partition with GRUB and all the other ones except the Windows EFI partition.
After cloning, both Ubuntu and Windows booted successfully until the next upgrades on Ubuntu ran os-prober and Windows Boot Manager disappeared from GRUB.

# The solution

After an entire day of useless searches this is the combination that worked for me:

1. Boot Windows Installation media or Hiren's Boot CD
2. Open a terminal and use diskpart to assign letters to the Windows partition and the EFI partition, from now on the first one will be C: and the second one will be D:
3. Run `bcdboot C:\Windows /s D: /f UEFI`
4. Exit and reboot, GRUB is still bootable because this procedure didn't overwrite GRUB files
5. On Ubuntu run Gparted, select the EFI partition and **make sure flags** `boot, esp, no_automount` **are enabled** (this was the actual solution and the most difficult part because nobody pointed this out in any guide I could find)
6. Run `sudo update-grub` to finally get Windows Boot Manager back

It may be necessary to delete all contents inside D: before step 3, not totally sure, but if the procedure above doesn't work you may have to try this way.
**BE CAREFUL:** you will completely delete GRUB and you will need to boot a live CD, chroot in your Ubuntu partition and restore GRUB:

#replace /dev/nvme0n1p5 and /dev/nvme0n1p4 with the appropriate devices
sudo mount /dev/nvme0n1p5 /mnt
sudo mount /dev/nvme0n1p4 /mnt/boot/efi
for i in /dev /dev/pts /proc /sys /run; do sudo mount -B $i /mnt$i; done
sudo chroot /mnt
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=ubuntu --removable
update-grub

Refs:
[https://forum.level1techs.com/t/reinstall-grub/134056](https://forum.level1techs.com/t/reinstall-grub/134056)
[https://web.archive.org/web/20250818050000/https://forum.level1techs.com/t/reinstall-grub/134056](https://web.archive.org/web/20250818050000/https://forum.level1techs.com/t/reinstall-grub/134056)


NOTE: the sequence provided above is an extract of everything I tried today, it should be enough to make the dual boot work again as all the other trials were useless, even rebuilding the BCD may be useless, since it always has been there. The key part was actually setting the flags of the partition.

I will appreciate feedbacks if anybody tries this fix or finds an easier solution.

https://redd.it/1r0k45z
@r_linux