Richard Weinberger
rw
"Enlightenment is man's release from his self-incurred tutelage. Tutelage is man's inability to make use of his understanding without direction from another. Self-incurred is this tutelage when its cause lies not in lack of reason but in lack of resolution and courage to use it without direction from another."
0
3
3
repeated
Richard Weinberger
rwIf you're into file systems, storage and the Austrian Alps, check this out:
https://lore.kernel.org/linux-fsdevel/20260701114306.GA17996@lst.de/
0
0
4
repeated
K. Ryabitsev-Prime 🍁
monsieuriconEDITED: You can follow the official incident here: https://status.linuxfoundation.org/incidents/3y1k8b4ky71t
4
56
61
Richard Weinberger
rw$ curl https://www.kernel.org/pub/linux/kernel/
<html>
<head><title>404 Not Found</title></head>
<body>
<center><h1>404 Not Found</h1></center>
<hr><center>nginx</center>
</body>
</html>
🤔
0
0
0
repeated
Jonathan Corbet
corbet...just in case anybody wonders why I have a rather dim view of the whole AI industry...
16
410
555
Richard Weinberger
rw
0
0
2
repeated
Jörg Seidel
lostgen@det.socialThat's absolutely sad to read. The CEO of @mullvadnet is not only financing the far-right Swedish Örebro party, but he even is their main financer. 70+% of their money is his donation. He is the reason why they go nationwide this year.
For obvious reasons i cease to trust this service. Also i do not finance parties that aim for forced deportations.
https://www.flamman.se/techprofil-ger-miljoner-till-orebropartiet/
6
32
0
repeated
GCC - GNU Toolchain
gnutools@fosstodon.orgGCC: Bump minimum GNU Make version to 3.81 released in 2006. Dont want to rush thing.
https://gcc.gnu.org/pipermail/gcc/2026-June/248407.html
0
1
1
Finally, there is a good chance that this a nothing-burger, since your UEFI is unlikely to enforce the expire date.
0
0
0
Richard Weinberger
rwThere is currently a lot of FUD regarding the expiration of Microsoft’s UEFI Secure Boot certificates this June. Many Linux users are understandably concerned that their machines will refuse to boot if Secure Boot remains enabled. I spent some time this morning sorting through the noise. Here is what you actually need to know:
👉 Expiration dates aren’t strictly enforced by default The UEFI specification and its reference implementation (Tianocore) do not mandate checking the expiration dates of certificates. The reasoning is practical: a computer needs to be able to boot even if the CMOS battery dies and the real-time clock (RTC) is broken. The caveat: Your specific motherboard or UEFI vendor might have implemented their firmware differently, which is where the uncertainty comes from.
👉 To be on the safe side, you can verify that the new Microsoft certificate is present in your system’s UEFI Secure Boot database. You can extract and inspect this directly from your Linux terminal:
# Extract the db variable
efi-readvar -v db -o db.esl
# Convert the signature list to certificates
sig-list-to-certs db.esl db_cert
# Inspect each generated db_cert-*.der file
openssl x509 -inform der -in db_cert-NNN.der -noout -subject -issuer -dates
(Check your specific db_cert-N.der files). You are looking for an output where the Common Name (CN) is “Microsoft UEFI CA 2023”.
👉 To ensure a smooth transition, your bootloader should be signed by both the old and the new Microsoft certificates. In my case, using shim from OpenSUSE, you can verify the signatures with sbverify:
sbverify --list /boot/efi/EFI/opensuse/shim.efi
repeated
Hacker News
hkrn@mstdn.socialIs AI ruining our skills? Early results are in – and they're not good
L: https://www.nature.com/articles/d41586-026-01947-1
C: https://news.ycombinator.com/item?id=48601286
posted on 2026.06.19 at 14:00:48 (c=0, p=5)
0
3
0
Richard Weinberger
rwThis reminded me of the computer science joke: how much is 1 plus 1? 1,9999
0
0
1