Is baeldung.com garbage?

Every now and then when I'm researching something linux related I'll see guides from baeldung.com pop up in the results. Today, I clicked one.

I was looking for some information on the keyring in fedora/gnome and came across what turned out to be a suspicious article.

https://www.baeldung.com/linux/unlock-keyring-fix

There's a section in there on disabling the keyring. The guide tells you to remove the password from your keyring, skip the warning that this means your passwords will be stored in cleartext, then says - Hey! You don't get prompted for a password anymore, the keyring is disabled!

Um....

> If we wish, we can disable the keyring feature by removing its password.

> By leaving the password blank, we disable the keyring feature

Sorry, but that isn't how it works. They do state that doing this "raises security concerns" but don't seem to make the connection that those concerns arise because the keyring is still enabled and doing its job, except now your passwords are stored in cleartext.

So not only do they not describe how to disable the keyring, they seem to think it's OK to guide people to doing this without much warning.

This was supposedly written by a human and reviewed by another human. I haven't looked into the author or reviewer much, but there's at least something there to indicate a real person. Even if it is a website that no longer exists, another website with an invalid ssl cert. There at least is an X account with posts going back a few years, though very rare.

However, don't think I'll be checking out any more of their articles.

Should I be willing to give them another shot?



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

rust-lang/rust is adopting an LLM policy

https://blog.rust-lang.org/inside-rust/2026/08/05/rust-langrust-is-adopting-an-llm-policy/

Second post I recently made about LLM usage policies but it's really just that I find the process of open source finding its way and adjusting to new realities rather interesting.

The "too long, didn't read" (Taken directly from the blog):

>What does the policy say?
>
>The policy summarizes itself this way:

>> It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create.

>Uses in the first category are allowed, sometimes requiring disclosure. Uses in the second category are heavily restricted.

(Edit: but I recommend reading the blog...it's a bit more nuanced than the summery)

Edit2: messed up the link, added now

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

KDE Material decoration with Locally Integrated Menu (and Search) sees its first official release
/r/kde/comments/1vg7lsr/material_decoration_with_locally_integrated_menu/

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

RPCS3 says 90% of PS3 emulator users run Windows, despite better Linux performance
https://videocardz.com/newz/rpcs3-says-90-of-ps3-emulator-users-run-windows-despite-better-linux-performance

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

the worlds most popular software synthesizer (Serum 2) now has a linux version
https://redd.it/1vgbser
@r_linux

Proxmox VE finally suports arm64!
https://forum.proxmox.com/threads/proxmox-virtual-environment-now-available-for-64-bit-arm-arm64.185526/

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

Officially ditched my dual boot. My PC is now 100% Windows free
/r/pop_os/comments/1vguuj5/officially_ditched_my_dual_boot_my_pc_is_now_100/

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

Distro Fighter: find your Linux distro & desktop
https://distrofighter.com/

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

GNOME Boxes Nightly — The next-gen rewrite of GNOME Boxes
https://nightly.gnomeboxes.org

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

HWiNFO64 style hardware monitoring software for Linux
https://github.com/pulpul-s/HWall

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

can anyone recommend a tiling window manager like hyprland for a non-arch distro like debian or fedora?

title. newish to linux so please be nice, i am here to learn.

i’ve been using omarchy for a little while, but everyone says its not great for beginners and i can kinda see that. i’m not totally lost, but i would prefer a point release distro over rolling. one thing that omarchy got me hooked on though is its tiling window manager (hyprland).

i noticed most window managers aren’t tiling, and was having trouble finding a good one for debian (which i hope to switch to, otherwise i may try cachyos).

i agree with most people that omarchy is kinda bloatware-ish and would prefer to install my own packages, but arch alone seems daunting.

cachyos, as i mentioned, is up there for my next distro, but i would def give debian/ubuntu forks or even fedora a shot if anyone has a good tiling manager that works with said distro.

again, thank you guys for all the help. still learning the ropes so i appreciate it!

hope the mods don’t mind this post, i know it says no support questions but i was hoping for more of a discussion, so thought it was okay. if its not i understand.

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

I Made a Plugin to Fix Quod Libet's Playlist Handling

Quod Libet is, as far as I've been able to find, the best native Linux music player. My biggest issue with it was the way playlists are handled. Coming from MusicBee on Windows, my playlists were nicely managed and maintained in a folder, which I could then sync to my other devices automatically along with the rest of my music library (via syncthing or whatever you use).



By default, Quod Libet has a few glaring issues with playlists:

Playlists can be imported but are only maintained in QL's internal files.
A plugin is needed to export playlists, and even with the plugin, you must manually export your playlists every time you add or remove a song, or change the order.
When a file has been moved or deleted, Quod Libet has no handling for this by default. It simply ignores that song without giving any type of warning or error.
Because of the above issues, syncing your playlists and library with other devices is a very manual pain in the neck.

I vibe-coded a plugin to fix all of the above and found it has vastly improved my experience. Please take a look, and hopefully it helps you as it has helped me.

https://github.com/Jukebox-Zulu/Quod-Libet-Playlist-Manager-Plugin

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

Some of my pass(1) entries stopped decrypting: a GnuPG regression that only triggers at exactly 4096 bits
https://dilluti0n.com/p/gnupg-tpm2daemon-rsa4096-bug/

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

AMD GFX1171 Support Merged For Mesa 26.3
https://www.phoronix.com/news/AMD-GFX1171-Mesa-26.3

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

I Ported CoLinux to X64 and expanded the driver to support all NT versions starting 5.2(XP) which atp is basically WSL but FOSS (Linux Kernel: 7.1.5 // NT: 10)
https://redd.it/1vh8x1p
@r_linux

I will try to install and use gentoo on an acer travelmate 290 from 2003
https://redd.it/1vh8ev7
@r_linux

Illinois's new law requires operating system providers to add age verification by 2028 including open-source projects
https://gov-pritzker-newsroom.prezly.com/gov-pritzker-signs-nation-leading-legislation-to-protect-illinois-children-on-social-media

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

This Quarter in KDE Digital Sovereignty: Q2 2026
https://blogs.kde.org/2026/08/06/this-quarter-in-kde-digital-sovereignty-q2-2026/

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

I got Howdy face unlock to also unlock my keyring, using the TPM — because a face can't be an encryption key

Howdy gives you face login on Linux. What it doesn't give you is a password — and gnome-keyring, KWallet and friends want one. So you get recognised by your face, and then asked for your password anyway. Which rather defeats the point.



I spent a while trying to fix this the obvious way and it can't work, so I want to explain why before the actual solution, because the why is the interesting part.



Why you can't just hash your face

The obvious idea is: take the face encoding, hash it, use that as the key.



Face encodings are fuzzy. Here are six enrolments of my own face, captured seconds apart on the same camera, compared pairwise:



encoding 0 vs 1 : 0.0829

encoding 0 vs 4 : 0.3609

encoding 1 vs 4 : 0.3846

encoding 2 vs 5 : 0.3166 (identical vectors would be 0.0000)

Every capture is a different 128-float vector. That's why face matching uses a distance threshold rather than equality — Howdy accepts anything under \~0.57. A hash of one encoding is unrelated to a hash of the next, so there's nothing stable to derive a key from.



And even if you solved the noise: your face isn't secret, and the model file sits on disk right next to whatever it would be protecting.



What actually works

The biometric doesn't become the key. It authorises the TPM to release one.



face match -> authorises -> TPM unseals -> a real, stable secret

(fuzzy) (hardware) (exact)

Seal your keyring password to the TPM, and have a PAM module unseal it after Howdy authenticates and hand it to the stack as PAM_AUTHTOK. gnome-keyring picks it up and unlocks. No prompt.



That's it. \~250 lines of C.



https://github.com/jibsta210/howdy-tpm



Face at the greeter, straight to desktop, keyring unlocked, nothing typed.

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

Why and how the Austrian Military moved to LibreOffice (Part 1)
https://blog.documentfoundation.org/blog/2026/08/07/why-and-how-the-austrian-military-moved-to-libreoffice-part-1/

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

WinBoat is alpha testing the GPU acceleration
https://redd.it/1vhugz4
@r_linux