九维我操你爹
https://fixupx.com/mattn_jp/status/1816756389232230740

咱们天天嘲笑日本人英语不好,结果到了开源界有人就觉得不是这么回事了
看到这段话其实感觉心情挺复杂的,坦率地讲我觉得自己心中多少也有日本人普遍英语很糟糕的成见。即便我自己也认识到了这段观点所提出的现象,但到头来我还是需要时刻纠正自己不要随便把别人看扁了
人家就算真的英语发音不太好吧,但最终是他们和外国人做的沟通最多,得到的评价最好(从这条评论所表达的个人印象来看)。反而是我们天天忙着细数谁谁谁把我们看扁了,同时自己又在心底鄙视人家这个看不起那个的。阿三棒子日子人随口就来,从来没有好好称呼过别人
#晚安世界
https://youtu.be/EDa9MRjH-mQ?si=yZXCeB3dXeh1Ez6H

上班带给我最大的帮助,是帮我在网上避免了好几次和别人吵架
实在是太累了,连生气的力气都没有了

在地铁上摇着晃着的时候,突然想到了这首歌
之前每周五总是会去大吃特吃一顿,想以此来给这一周划上个圆满的句号
今天是第一次无处可去的日子,但是却不觉得失望,因为身心都被这首歌词十分简单的歌治愈了

尽管简单,却一点也不简单呢
苹果测试工程师的日常
hot take: Secure boot is nothing more than chains that shackle OEM-ed devices from its users, who are supposed to have full access to their own devices. It only erects barriers to other distros which are not certified by Microsoft, since users are no longer…
Which brings us to point number 2: When Rufus is asking you to disable Secure Boot, as a temporary measure, so that you can boot the UEFI:NTFS bootloader, it's not because this bootloader should be considered unsafe, or because we were too lazy/too cheap to get it signed for Secure Boot, or even (as some people seem keen to suggest) out of spite because we dislike Secure Boot (which is incorrect: We do like the principle behind Secure Boot. We just don't like the clear abuse of power that is being demonstrated when a single entity; Microsoft, is left in control of it and abuses it to promote a nefarious agenda). No, the ONLY reason haven't been able to provide a signed UEFI:NTFS bootloader until Rufus 3.17, which would avoid requesting that you disable Secure Boot, is because Microsoft (again the only entity that controls the Secure Boot signing process) has unilaterally decided, for no reason that stands the test of scrutiny, that anything licensed under GPLv3 cannot be signed for secure boot, ever.

Microsoft has decided it doesn't like the GPLv3 and, in a clear abuse of power created a signing process that forbids the submission of anything that is GPLv3. Of course, Microsoft tried to "justify" their stance with a half baked tirade about how the GPLv3 would ultimately require them to relinquish their private keys, but that reasoning can easily be demonstrated to be utter bullshit when you also know that Microsoft has no qualms signing Linux shims, which, clearly, it should not sign, since these should logically be subjected to the same "alleged" relinquishing of private keys that the GPLv3 is supposed to entitle its users to, and therefore, if Microsoft's reasons are to be believed, having said shims load GPLv3 bootloaders such as GRUB (which they do) can only result in someone eventually demanding that the shims' private signing keys are relinquished, therefore completely defeating Secure Boot...


https://github.com/pbatard/rufus/wiki/FAQ#user-content-Why_do_I_need_to_disable_Secure_Boot_to_use_UEFINTFS FAQ
苹果测试工程师的日常
https://www.binarly.io/blog/pkfail-untrusted-platform-keys-undermine-secure-boot-on-uefi-ecosystem
hot take:
Secure boot is nothing more than chains that shackle OEM-ed devices from its users, who are supposed to have full access to their own devices. It only erects barriers to other distros which are not certified by Microsoft, since users are no longer able to boot from them effortlessly. (It is also quite intimidating. Users get warned that they must disable SECURE boot in order to boot from distros they are trying to reach!)
Even if we put aside prejudices against Secure Boot and acknowledge the merit in its technical considerations, its track record is concerning. The numerous vulnerabilities introduced by Secure Boot demonstrate that while it may be sound in theory, its practical implementations have consistently fallen short, making it hard to regard the concept as truly beneficial in practice.

Secure Boot 不过是彻头彻尾的商业产物,它让用户失去了对设备的完整控制,人为地设起了一道壁垒,阻碍用户自由选择他们喜欢的发行版(你将要安装的发行版没有经过我们的认证,因此你必须要关闭“安全”启动才能从这些发行版进行引导和启动!)
即便放下对 Secure Boot 是一种垄断行为的无理指控,试图肯定 Secure Boot 背后的技术考量确实存在道理。历史上数次因 Secure Boot 引入的严重安全风险也在不断地说明就算 Secure Boot 是个好点子,但它从来没被好好地实践过。而一个总是在实践时出现问题的点子从来都不是什么好点子
https://lwn.net/Articles/938149/

The plan, in short, calls for rebuilding each library that includes time_t somewhere in its ABI, and renaming the library by adding t64 to its name (thus allowing the older library to stay in place initially). Once all packages have been rebuilt to use the new libraries, the old ones can be removed and the t64 suffix taken off again.


升级 ubuntu 24.04 以后吓了一跳……
Back to Top