The website is actually hosted on GitHub pages.

Just type in a random non-existing path and it shows the GitHub pages 404 path.

I'm having no problems with donating to OSS projects, yet what always prevents me from doing so is when such projects are not transparent where my donation money actually goes.

Yet, the average donations we receive are around 100 euros per month. A sum that doesn’t even cover server costs or the resources we use.

Well, I see no linked explanation where this money goes or why the server costs are so high, which is immediately a red flag for me.

under Wikipedia's entry for Secure boot

What's the first thing under the "Secure boot" section? The section that it automatically scrolls to when clicking my link?

Well the website (and the guy maintaing it) is pretty old. I think the blog posts reach back till Windows Vista. The guy itself wrote some books about Win95 so he has some experience.

The site is quite popular in Germany and the information is usually good summarized and helpful IMHO.

Anyway as always I recommend an adblocker when using the internet.

It's so secure that the first thing under Wikipedia's entry for Secure boot is Secure boot criticism

Yes this is a real, I'm not joking.

You're in linuxmemes did you not expect a meme? xD

Also: Yes it's a meme based on a true story (see the other comments for more details)

The meme itself is based on https://knowyourmeme.com/memes/historical-battle-shitposts-decisive-victory

AFAIK a new battery + entering the Bitlocker recovery key fixed the problems.

Usually these batteries hold for years. I have a 15+ year old laptop where I had to replace the battery after ~10 years.

However the affected laptops are now a few years old, aren't designed properly (I heard weird stuff happening like adding additional RAM somehow causes the display to fail) and somehow just have a CR2016 battery installed, not a bigger CR2032. And yes these are buisness-laptops designed for companies -.-

Yes, multiple of our Windows laptops today couldn't boot and displayed a BitLocker error message and all affected laptops somehow had an empty BIOS battery...

Me on my de-googled phone:

Diese Kommentarsektion ist nun Eigentum der BRD.

I also personally ask myself how a PyPI Admin & Director of Infrastructure can miss out on so many basic coding and security relevant aspects:

• Hardcoding credentials and not using dedicated secret files, environment variable or other secret stores
• For any source that you compile you have to assume that - in one way or another - it ends up in the final artifact - Apparently this was not fully understood (".pyc files containing the compiled bytecode weren't considered")
• Not using a isolated build process e.g. a CI with an isolated VM or a container - This will inevitable lead to "works on my machine" scenarios
• Needing the built artifact (containerimage) only locally but pushing it into a publicly available registry
• Using a access token that has full admin permissions for everything, despite only requiring it to bypass rate limits
• Apparently using a single access token for everything
  • When you use Git locally and want to push to GitHub you need an access token. The fact that article says "the one and only GitHub access token related to my account" likely indicates that this token was at least also used for this
• One of the takeaways of the article says "set aggressive expiration dates for API tokens" - This won't help much if you don't understand how to handle them properly in the first place. An attacker can still use them before they expire or simply extract updated tokens from newer artifacts.

On the other hand what went well:

• When this was reported it was reacted upon within a few minutes
• Some of my above points of criticism now appear to be taken into account ("Takeaways")