class=”article first_main_article” readability=”73″>Do you remember those two
polemics which we fought us? As a going to be impossible, since the discussion has continued in crescendo, leaving details of interest and the father of Linux once again showing its character and attention, putting the user first: Linux will jump through hoops of Microsoft’s Secure Boot . And point.
that you walk a little clueless, start the story at the beginning, when it was revealed that Windows 8 would incorporate secure boot feature using UEFI, which basically serve as a replacement to existing and decrepit after BIOS upgrade system security, preventing software startup unsigned and potentially dangerous .
What’s wrong with the above? That the vast majority of computers sold in the world come with Windows pre-installed, and Microsoft is signing keys UEFI security on devices with its operating system . In short and possibilities “unofficial” apart, who would like to install a Linux distribution on your newly bought computer with Windows 8 could not, at least a priori.
As you can imagine, the mess was monumental, even though from Microsoft were quick to calm down. The official solution passed through reliable Linux distributions that go through the hoop Microsoft , requesting certified keys for this purpose. From there, each went his way distribution, Fedora being the most active in this respect (the first to pay the license to generate their own keys, offering them to other community GNU / Linux). Even the Linux Foundation came into play.
So, the problem was gone, and in fact the latest releases of the most popular distros already support Microsoft’s Secure Boot . Without thier, although the problem was gone, you could do something to improve the implementation of Microsoft’s UEFI (stating the distinction and repetition) in GNU / Linux, preventing developers work distros if firms included directly into the kernel . That’s at least what he must have thought the Red Hat engineer who dared last week with the request. But …
Linux
response and know not (more details at the link). What if Red Hat wanted, could deploy your kernel, but not the kernel he keeps . Mainly because it is not a standard, but a “thing” that Microsoft’s own security will not but control . To make matters worse, Microsoft, only certification authority for now, just sign binary . Once again …
And again you can imagine the response of Linus (expletives included, of course). But in addition to take fire from his mouth, the distinguished finlandéis took something of his genius-productive in the sense of the word, and suggested some changes, “ instead of trying to please Microsoft, see how we can increase security really “(we will look and see if something interesting comes out of there). The discussion, however, continues, now spread throughout the network
And what is it? In that while Linus send, “it” is not within the Linux code . Or at least not as it will now arise. And how does that affect users of GNU / Linux? anything . Why I rewrite on a subject that neither going nor coming to using GNU / Linux and also can not explain or understand without technical knowledge of many lack? Because now the end has been imposed, would be the answer. But I have not very clear.
