Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #272291
| From | Dexter Filmore <Dexter.Filmore@gmx.de> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | shim / MS updates |
| Date | 2024-08-18 19:20 +0200 |
| Message-ID | <JcRJn-5UWI-3@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Recent Windows updates caused certain bootloaders to make the blacklist, I just had an argument that went like: why wasn't there a shim update when MS announced this in April? And then someone kept insisting that when the Secure Boot feature was designed Linux distributors did not name an authority for signing and thus it was their own fault. Sounds wrong to me as usually MS strongarms the rest of the world out of platform control ans I suspect much the same happened with Secure Boot, but I wouldn't know. Does someone know how this went politically "back then"? Dex
Back to linux.debian.user | Previous | Next | Find similar | Unroll thread
shim / MS updates Dexter Filmore <Dexter.Filmore@gmx.de> - 2024-08-18 19:20 +0200
csiph-web