Slashdot Mirror


FreeBSD Team Begins Work On Booting On UEFI-Enabled Systems

An anonymous reader writes "The FreeBSD project has begun the process of making it possible for the operating system to run alongside Windows 8 on a computer which has secure boot enabled." Linux distros have taken to using a minimal loader, signed by Microsoft, to enable booting on UEFI systems with secure boot. "Indeed we will likely take the Linux shim loader, put our own key in it, and then ask Microsoft to sign it," says developer Marshall McKusick in the linked IT Wire article. "Since Microsoft will have already vetted the shim loader code, we hope that there will be little trouble getting them to sign our version for us."

248 comments

  1. Well I'll be... by fustakrakich · · Score: 3, Informative

    I did not know Microsoft won that battle.

    --
    “He’s not deformed, he’s just drunk!”
    1. Re:Well I'll be... by kthreadd · · Score: 3, Funny

      Won what battle? There is no battle. They just managed to get their key into the hardware manufacturers and happen to conveniently sell access to that. Nothing stops anyone else from doing the same.

    2. Re:Well I'll be... by gl4ss · · Score: 1

      I did not know Microsoft won that battle.

      well.. won and won.. they kind of lost if they had to start accepting shim loaders. kind of defeats the whole point.

      --
      world was created 5 seconds before this post as it is.
    3. Re:Well I'll be... by Anonymous Coward · · Score: 3, Insightful

      Hahahahaha. The rich and poor are equally prohibited from sleeping under bridges... Free-market ideology induced brain damage at its best. Or was this sarcasm? Then I am sorry.

    4. Re:Well I'll be... by mrbluejello · · Score: 1

      As soon as you can push through 10 million units of PC sales through an OEM with your OS pre-installed, you can stop having Microsoft sign your shim and deal directly with the OEM.

    5. Re:Well I'll be... by kthreadd · · Score: 1

      Well that's how the CA business work; just that in this case it's about hardware manufacturers, not browser/OS vendors. I don't think it's a good idea from a security perspective since it trusts things by default, and can have really bad consequences when a CA is compromised. But that's how it work for now.

    6. Re:Well I'll be... by Anonymous Coward · · Score: 0

      What "battle"? PC x86 motherboards are designed to Microsoft's specification to run Windows and have been since IBM lost control of the PC standard. Free OSes just piggybacked on cheap x86 motherboards to take off. Ancient history.

      If MS wants to change their standards and the OEMs agree, nobody else has any say in the matter. (Ooh, let's watch the libertarians here break out in hives.)

    7. Re:Well I'll be... by icebike · · Score: 4, Informative

      No it defeats no point, and Microsoft is free to accept or deny just about anything. Properly implemented secure boot increases your security by letting you decide what the machine should boot and prevent it from booting unknown or potentially malware infected operating system. That is a good feature. It has nothing to do with preventing competition.

      Deciding that one, and only one company can sign shims, can't be considered anything but anticompetitive.

      Then, forcing that company to sign boot shims from Linux and FreeBsd to avoid illegal restraint of trade charges, pretty well eliminates any benefit the plan might have had. Is Microsoft going to sign every backroom version of Linux and every clone of FreeBsd, ot did the just pare down the competition teo a few major distros?

      --
      Sig Battery depleted. Reverting to safe mode.
    8. Re:Well I'll be... by recoiledsnake · · Score: 4, Insightful

      You could start a signing company now, and if people trust you, they will add your keys, and you may even get traction from the OEMs. Nothing in secure boot prevents that except that no one wants to create a signing organization because they don't want to be bothered. In face Secure Boot MS Spec requires OEMs to enable users to add their own keys or even remove Microsoft's if they don't trust it.

      --
      This space for rent.
    9. Re:Well I'll be... by kthreadd · · Score: 1

      It is completely up to the hardware manufacturers which keys they want to preinstall. My preference would be none, and let the user install it. Here Microsoft acts as a CA, just like any other CA do. Anyone else can sign, but Microsoft was one of the few with the operation in place to go out and deal with many of the vendors.

    10. Re:Well I'll be... by AK+Marc · · Score: 1

      If MS wants to change their standards and the OEMs agree, nobody else has any say in the matter. (Ooh, let's watch the libertarians here break out in hives.)

      I thought companies bullying the consumer with anti-competitive behavior was "freedom" and supported by the Slashdot libertarians.

    11. Re:Well I'll be... by Anonymous Coward · · Score: 3, Insightful

      And whoops, you just lost your license to distribute OEM Windows copies. How unfortunate. But that would never ever happen, right?

    12. Re:Well I'll be... by Anonymous Coward · · Score: 0

      In that respect, secure boot does not provide any more security than turning off booting from external devices and setting a BIOS password. But boot virii/malware are not very common anyway. For everything else: An exploitable OS/browser/mail client is still exploitable even when signed by somebody. This bullshit is all about control and has not much to do with security.

    13. Re:Well I'll be... by kthreadd · · Score: 1

      Well it works more or less the same as the https thing in the web browser. Everything is exploitable, but properly managed can at least minimize the risk.

    14. Re:Well I'll be... by Anonymous Coward · · Score: 0

      Well that's how the CA business work; just that in this case it's about hardware manufacturers, not browser/OS vendors. I don't think it's a good idea from a security perspective since it trusts things by default, and can have really bad consequences when a CA is compromised. But that's how it work for now.

      I wish everyone understood this point. It is very important.

      If someone with physical access to the machine (you!) could (had to) set what signing keys it accepted in the TPM, this would be great tech.

    15. Re:Well I'll be... by SuricouRaven · · Score: 2

      For now.

      They dont 'have' to accept shim loaders. They are doing so for now, to minimise the backlash. There's no assurance they'll continue to do so in future, or (more likely) that they won't start imposing onerous requirements in the name of 'security' like mandating that any qualifying bootloader be incapable of loading an OS that allows unsigned drivers.

    16. Re:Well I'll be... by gigaherz · · Score: 0

      I don't think you need strong AI to make a script that goes "if content contains "bing", mark for deletion", although it may have a few false positives.

    17. Re:Well I'll be... by gigaherz · · Score: 1

      It's not about the license: if you don't trust Microsoft's key, then you can't possibly trust Windows 8. It doesn't matter if you buy OEM licenses, they won't boot!

    18. Re:Well I'll be... by Anonymous Coward · · Score: 0

      Windows 8 doesn't require secure boot.

    19. Re:Well I'll be... by Rockoon · · Score: 5, Insightful

      you just lost your license to distribute OEM Windows copies.

      No you didn't...

      ..you just lost Windows Certification.

      Another way to lose Windows Certification is not allowing the end user to disable Secure Boot.

      In other words, Windows Certification actually protects your rights.

      --
      "His name was James Damore."
    20. Re:Well I'll be... by ldobehardcore · · Score: 1, Troll

      Too bad the user can't manage his own hardware now. We're at the mercy of the mobo manufacturers, as they decide who's keys are trusted by default (ie microsoft ONLY). If I have to go to microsoft in order to be allowed to boot BSD on my own motherboard, then my property rights are being violated. I'm not leasing or borrowing my mobo, I've bought it. That means nobody else has a right to tell me I can't do whatever I want with it (within legal limits).
      The only feature of UEFI so far is to wrest control from the actual owner of the hardware. This is just as bad as DRM. Nobody woke up this morning and said to themselves "I wish I could buy a desktop computer that let me do less with it than my current machine." Nobody goes to iTunes thinking "I wish I could buy a song that plays on fewer devices than what I have" and nobody thinks "I wish I could buy a movie that plays on my cellphone, but I sure would be pissed if it could play on my TV, Kindle and laptop too"

      UEFI so far is only a bad thing. I currently own a motherboard that claims to have "dual uefi" whatever that means, and I still can't disable secureboot even with a manual. That's simply not an option. The manufacturers, in collusion with microsoft, have figured out a way of forcing me to use windows 8. I don't want to use windows 8. And my only alternative is counting my current mobo as a loss of $120, and buying either a used mobo (who knows how damaged it is), or a mobo that's been sitting in a warehouse a few years (better than the former, but still iffy. Why are they there in the first place? Why haven't they been sold yet?)

      --
      Hectice, baby, Mercator says hello to you
    21. Re:Well I'll be... by aaaaaaargh! · · Score: 2

      Properly implemented secure boot increases your security by letting you decide what the machine should boot

      Exactly. Secure boot is not properly implemented. A proper implementation would allow you to install anything you like after flipping a manual switch.

    22. Re:Well I'll be... by gtirloni · · Score: 1

      How much is M$ charging for access to that?

      --
      none
    23. Re:Well I'll be... by nukenerd · · Score: 2

      [AC wrote] you just lost your license to distribute OEM Windows copies.

      [Rockoon wrote] No you didn't... ..you just lost Windows Certification.

      Amounts to the same thing. With the exception of a tiny niche market, OEMs cannot make a living by selling PCs without Windows at its bulk discounted price, nor without a Windows certification sticker on it. While it would not bother me, Joe Public just won't buy a PC unless they see "Designed for Windows" on it.. Withdrawing either of those priviledges are weapons Microsoft has to control the market.

    24. Re:Well I'll be... by gl4ss · · Score: 1

      can ms revoke the signing on the shim that you can use to boot arbitrary code you want?

      this is what I was referring as defeating the whole point.

      --
      world was created 5 seconds before this post as it is.
    25. Re:Well I'll be... by smash · · Score: 1

      Geeks can just install their own keys.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    26. Re:Well I'll be... by devent · · Score: 2

      > In other words, Windows Certification actually protects your rights.

      Only because it's currently in Microsoft's interests.
      And that come from the anri-competition fines from the EU.

      So you should thank the European Commission.
      http://en.wikipedia.org/wiki/European_Union_Microsoft_competition_case

      --
      http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
    27. Re:Well I'll be... by Rockoon · · Score: 2

      OEMs cannot make a living by selling PCs without Windows at its bulk discounted price, nor without a Windows certification sticker on it.

      The only consumers that care about Windows Certification are enterprise customers...

      Seriously.. do you think your grandmother makes sure that the laptop has Windows Certification before she buys it?

      Translation: You really havent thought about this at all, but have just jumped at a shallow poorly considered excuse to hate at Microsoft again.

      --
      "His name was James Damore."
    28. Re:Well I'll be... by kthreadd · · Score: 1

      $99

    29. Re:Well I'll be... by Rockoon · · Score: 2

      Exactly. Secure boot is not properly implemented.

      Its properly implemented. you are just putting an undue amount of weight to the hand wavers that don't really have an argument:

      Te get windows certification, the end user must be able to:

      a) disable secure boot
      b) install their own keys

      What extra implementation restriction did you have in mind?

      --
      "His name was James Damore."
    30. Re:Well I'll be... by Rockoon · · Score: 1

      You seem to be under the impression that the keys are tested vs a remote certificate authority during bootup.

      In other words, you do not seem to actually understand very much. The certificate authority is UEFI, not some server on the internet.

      --
      "His name was James Damore."
    31. Re:Well I'll be... by nukenerd · · Score: 1

      OEMs cannot make a living by selling PCs without Windows at its bulk discounted price, nor without a Windows certification sticker on it.

      The only consumers that care about Windows Certification are enterprise customers... Seriously.. do you think your grandmother makes sure that the laptop has Windows Certification before she buys it?

      Yes. Possible scene in PCWorld :-

      Grandmother/JoePublic : "Nice colour, but does it run Windows?"

      Salesman : "Of course it does madam/sir, they all do!"

      GM/JP : "So why doesnt it have that 'Designed for Windows' sticker on it like those others do?"

      Salesman : "Just a detail madam/sir, Microsoft are very strict, just one minor thing, nothing to worry ..."

      GM/JP : "Not sure about that then"

      Salesman : "You mentioned those others, that's a nice one over there ...."

    32. Re:Well I'll be... by Anonymous Coward · · Score: 1

      b) install their own keys

      Sooo.... Why do the different Linux distributions need to get MS to accept those shims again ? I mean, they do not go that troublesome way for nothing.

      Maybe something else further down the road that does not want to cooperate when the MS key is not at its "rightful" place -- and thus making a mockery of that above rule ?

    33. Re:Well I'll be... by Rockoon · · Score: 1

      GM/JP : "So why doesnt it have that 'Designed for Windows' sticker on it like those others do?"

      Your grandmother is not asking that question, and doesnt even know that such a sticker exists.

      You are stretching farther and farther into an absurd reality in order to hate Microsoft on this one. With all the valid reasons to hate Microsoft, why are you so intent on manufacturing a fantasy in order to create another one out of vapor?

      --
      "His name was James Damore."
    34. Re:Well I'll be... by RaceProUK · · Score: 1

      99.999% of real conversations in PC World:

      GM/JP: Can I check my e-mail on it?

      Salesman : Yes.

      GM/JP: Can I watch cat videos on it?

      Salesman : Yes.

      GM/JP: Shut up and take my money!

      --
      No colour or religion ever stopped the bullet from a gun
    35. Re:Well I'll be... by RaceProUK · · Score: 2

      Why do the different Linux distributions need to get MS to accept those shims again ?

      They don't, but you can't put a price on convenience.

      --
      No colour or religion ever stopped the bullet from a gun
    36. Re:Well I'll be... by Anonymous Coward · · Score: 0

      And if content does not contain Bing, refuse to open the device. Content control is even more important than hardware control, and they're really aiming at widescale Digital Rights Management with Microsoft owned and managed keys with the whole "Trusted Computing" technology.

    37. Re:Well I'll be... by msauve · · Score: 1

      How is revocation handled?

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    38. Re:Well I'll be... by 1s44c · · Score: 1

      Of course you can suggest whatever you want. Just don't expect them to do something which is impossible to do (well, at least until strong AI is developed).

      Can we get that strong AI to write comments too? It would really boost the signal to noise ratio.

    39. Re:Well I'll be... by 1s44c · · Score: 1

      If the system is rigged in such a way you have to trust any Microsoft code then it's a terrible system.

      There is nothing secure about UEFI as implemented. Let me set my own keys without having to trust any vendor and I'll consider it secure.

    40. Re:Well I'll be... by 1s44c · · Score: 1

      Well it works more or less the same as the https thing in the web browser. Everything is exploitable, but properly managed can at least minimize the risk.

      The CAs behind 'https' can't be trusted one little bit. The only protection in using https instead of http is from casual packet sniffing.

      The only way to fix it is to have a trustworthy CA run in a country that doesn't spy on everything and run by incorruptible people. It's not going to happen.

    41. Re:Well I'll be... by 1s44c · · Score: 1

      How is revocation handled?

      I don't believe it can be. Nothing outside the machine is checked at boot time.

      This looks like CSS over again. half baked security that ultimately trusts people who screw up a lot.

    42. Re:Well I'll be... by 1s44c · · Score: 1

      The battle is to fix that.

      I believe Linux now runs on far more servers than Windows does, will any hardware manufacturer give up their share of the huge Linux market to their competition?

    43. Re:Well I'll be... by moronoxyd · · Score: 2

      If the UEFI firmware is implemented correctly, it offers an option for someone with physical access to the machine to see a list of the keys, add and (probably) remove keys at will.

      Actually, if I'm not mistaken Microsoft demands this for machines to get the Windows 8-Logo.

    44. Re:Well I'll be... by Anonymous Coward · · Score: 0

      $99

      I'm willing to pay $199 if I can get access to both the public and the private key.

    45. Re:Well I'll be... by moronoxyd · · Score: 1

      No. If the END USER disables the Microsoft signing key, it's not the fault of the OEM.

      Also, neither of these two would know that I or you disabled the Microsoft key.

    46. Re:Well I'll be... by moronoxyd · · Score: 1

      My preference would be none, and let the user install it.

      No keys pre-installed would mean that 95% of the systems would run without secure boot, as most people couldn't be bothered to go into the UEFI setup to add a ... "whatchacallit? Key? A few letters and numbers? What good is that?"

    47. Re:Well I'll be... by moronoxyd · · Score: 3, Informative

      Too bad the user can't manage his own hardware now. We're at the mercy of the mobo manufacturers, as they decide who's keys are trusted by default (ie microsoft ONLY). If I have to go to microsoft in order to be allowed to boot BSD on my own motherboard, then my property rights are being violated.

      You can deactivate secure boot.
      You can add other signing keys to the list used by the UEFI firmware.
      You can remove the Microsoft key.

      So what's your problem?
      Actually, Microsoft DEMANDS all these things from an OEM before they can put the niftly little 'designed for Windows 8' stickers on their machines.

    48. Re:Well I'll be... by moronoxyd · · Score: 1

      b) install their own keys

      Sooo.... Why do the different Linux distributions need to get MS to accept those shims again ? I mean, they do not go that troublesome way for nothing.

      Because they don't want to go to each and every mainboard and OEM manufacturer and convince them to add their key to the list.
      They could, if they wanted.

    49. Re:Well I'll be... by moronoxyd · · Score: 1

      Maybe an update to the UEFI firmware could revoke/add keys?
      We had BIOS updates add/remove functionality for years, so I would guess that the same is possible for UEFI updates.

    50. Re:Well I'll be... by Gadget_Guy · · Score: 3, Informative

      Why do the different Linux distributions need to get MS to accept those shims again ?

      To make it easier to install the OS without having to require that people install keys. Since there would be a variety of interfaces in the different motherboards, it would make it difficult to write generic documentation to tell lay people what to do. That hardly makes for a plug-n-play experience, and brings us back to the good-old-days of overly complicated operating system installations.

    51. Re:Well I'll be... by kthreadd · · Score: 1

      Technically they sign your key.

    52. Re:Well I'll be... by evilRhino · · Score: 1

      You could always make your own CA, but maybe you can't trust yourself.

    53. Re:Well I'll be... by Curunir_wolf · · Score: 1

      UEFI so far is only a bad thing. I currently own a motherboard that claims to have "dual uefi" whatever that means, and I still can't disable secureboot even with a manual.

      I haven't seen a motherboard yet without the option for disabling secureboot and managing the uefi with a shell. Maybe you could mention which board this is so the rest of us can avoid it.

      --
      "Somebody has to do something. It's just incredibly pathetic it has to be us."
      --- Jerry Garcia
    54. Re:Well I'll be... by Anonymous Coward · · Score: 0

      IIRC, VeriSign charges the $99.

    55. Re:Well I'll be... by jbolden · · Score: 1

      Microsoft wants to stop root kits. They want to be able to offer secure environments for DRM content. Microsoft doesn't care about people who want to boot Linux at all. So they are fine signing those because that customer base will self support on root kits. Where is the conflict? That only defeats the point if you start by assuming that Microsoft was lying about their intentions. If you start by assuming that everyone was telling the truth and there is no big conspiracy then it is perfectly fine.

    56. Re:Well I'll be... by jbolden · · Score: 1

      No they are going to sign a few version of boot loaders and then not care about the rest.

    57. Re:Well I'll be... by jbolden · · Score: 1

      Sooo.... Why do the different Linux distributions need to get MS to accept those shims again ? I mean, they do not go that troublesome way for nothing.

      Because they want to be able to boot on systems that haven't disabled secure boot and haven't installed another key.

    58. Re:Well I'll be... by jbolden · · Score: 1

      There is no revocation. Once code is signed to a particular key, it is signed forever.

    59. Re:Well I'll be... by jbolden · · Score: 1

      You can install your own keys.

    60. Re:Well I'll be... by EvanED · · Score: 1, Troll

      But boot virii/malware are not very common anyway.

      And of course the way to respond to a potential threat is to do nothing until it's common, then scramble to find a half-assed solution.

    61. Re:Well I'll be... by ArcadeMan · · Score: 1

      If you do that, you'll miss a lot of funny quotes.

    62. Re:Well I'll be... by F.Ultra · · Score: 1

      So you mean that JoePublic knows that the machines run Windows now?

    63. Re:Well I'll be... by F.Ultra · · Score: 1

      Of course that Microsoft was behind Secure Boot in the first place had nothing to do with it either :)

    64. Re:Well I'll be... by F.Ultra · · Score: 1

      There is a revocation database stored in UEFI that apparantly Microsoft can update, or perhaps the HW manufacturer has to push out an update to UEFI, I don't know but the UEFI specs contains details that there must be such a database and that it can be updated.

    65. Re:Well I'll be... by 1s44c · · Score: 1

      You can install your own keys.

      Can I really? Because other people say I can't without running windows first.

    66. Re:Well I'll be... by Anonymous Coward · · Score: 0

      Not only all of the above, but microsuck has done such a wonderful job of protecting their certificate authorities in the past....

    67. Re:Well I'll be... by msauve · · Score: 1

      You obviously don't understand it. There certainly is the capability for key revocation. The question is how that will work administratively.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    68. Re:Well I'll be... by bluefoxlucid · · Score: 1

      Except they implemented an "Increases your Security" feature that prevents you from booting another OS. Then they sign a loader that boots any other OS. I could get the Linux shim loader to boot FreeBSD easy enough--Linux can boot FreeBSD by kexec, after all. A little quick-and-dirty will make it boot fine.

    69. Re:Well I'll be... by bluefoxlucid · · Score: 1

      The CA just signs your public key. They don't have access to the bit of secret needed to actually snoop your traffic; what they can do is sign another piece of secret claiming to belong to you, which is highly visible and obvious.

    70. Re:Well I'll be... by Anonymous Coward · · Score: 0

      They were forced to "demand" that.

      If they had their way, no one could ever disable it or remove the key...

    71. Re:Well I'll be... by Anonymous Coward · · Score: 0

      You can deactivate secure boot.
      You can add other signing keys to the list used by the UEFI firmware.
      You can remove the Microsoft key.

      For now...

      Just wait and see...

    72. Re:Well I'll be... by Anonymous Coward · · Score: 0

      And what would that "convenience" be, exactly ?

      It looks like its enough for the freedom-loving community that Linux is to go that troublesome "please MS, sign the shim we have created" road ...

      moronoxyd (1000371)

      Because they don't want to go to ...

      Hmmm ... So those keys need to be added to a list eh ? Than what is that "b) install their own keys" about if that list is all that is used ?

      Gadget_Guy (627405)

      To make it easier to install the OS without ..

      Really ? If in the past years anyone installing an OS or wanting to play a game was able to enter some authentication-key than someone who installs a flavour of Linux should be able to enter a "key" into an UEFI slot.

      Besides that: The main key should than not be defined by MS, but by the same organisation who created the UEFI standard.

      by jbolden (176878)

      Because they want to be able ...

      The same answer as the above.

      --

      Bottom line: It looks like that "b) install their own keys" is either not the solution, or much harder than it should be ...

      P.s.
      Can a user remove keys, like the MS one ? No ? Bad omen ...

    73. Re:Well I'll be... by RaceProUK · · Score: 1

      And what would that "convenience" be, exactly ?

      The convenience of being able to yodel the Copacabana, obviously.

      --
      No colour or religion ever stopped the bullet from a gun
    74. Re:Well I'll be... by Anonymous Coward · · Score: 0

      Except some OEMs implement the ability to disable secure-boot by only giving you an option to completely disable UEFI and boot a legacy BIOS. At which point, your system will no longer boot your licensed and installed Windows 8. So much for dual-boot.

    75. Re:Well I'll be... by jbolden · · Score: 1

      That has nothing to do with running anything. It is going to be a UEFI procedure the OS shouldn't be able to change it.

    76. Re:Well I'll be... by jbolden · · Score: 1

      Yes obviously I don't understand. So where are these references to revocation mechanisms?

    77. Re:Well I'll be... by Anonymous Coward · · Score: 0

      If the UEFI firmware is implemented correctly, it offers an option for someone with physical access to the machine to see a list of the keys, add and (probably) remove keys at will.

      Actually, if I'm not mistaken Microsoft demands this for machines to get the Windows 8-Logo.

      That does seem to be the case. I was wrong, thanks for the correction. Microsoft apparently claims you should have the ability to do this, but it appears that its often intentionally hidden and undocumented if possible at all. Personally I'd like to see secure boot enabled, but with no default keys, so the UI to set keys has to be easy, gets tested, and everyone would know about it.

      On the WindowsRT arm machines, it looks like there are no choices at all.

    78. Re:Well I'll be... by Anonymous Coward · · Score: 0

      From what I've heard, that doesn't apply to ARM machines. And I don't know what his problem is, but my problem is placing the decision of what OSes can install or not, even if it's just the default settings, into Microsoft's hands. It's a matter of principle; I don't trust them, they should not have the right to act as gatekeeper in ANY way if I have chosen not to associate with them. And this added "security" is hardly useful to the average user. Secure boot is an obvious attempt at a power play by Microsoft, and it worked (unlike most of their business strategies since Gates left).

    79. Re:Well I'll be... by msauve · · Score: 1

      1.
      2.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    80. Re:Well I'll be... by theskipper · · Score: 1

      $699 of course. If at first you don't succeed...

    81. Re:Well I'll be... by sexconker · · Score: 0

      No it defeats no point, and Microsoft is free to accept or deny just about anything. Properly implemented secure boot increases your security by letting you decide what the machine should boot and prevent it from booting unknown or potentially malware infected operating system. That is a good feature. It has nothing to do with preventing competition.

      How is this modded troll? It's 100% correct.

      What is it about Secure Boot that turns Slashdot into a rabid pile of flailing retards (more so than usual)?

      UEFI is not Secure Boot. UEFI is good. Secure Boot is good. We have a working "solution" (a signed bootloader and a trusted key, just as it was intended) for Linux. The generic "solution" is for you to add keys to your devices as trusted. Desktops and laptops with the Windows 8 logo let you add your own keys.
      If you bought a shitty, locked-down tablet, your beef is with the device and the company that made it, not Secure Boot or MS, and certainly not UEFI.

    82. Re:Well I'll be... by jbolden · · Score: 1

      Good show. I stand corrected.

    83. Re:Well I'll be... by X0563511 · · Score: 1

      Strange, you speak as if "geeks" was a single person and not a wide reaching group of people with vastly varied tendencies.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    84. Re:Well I'll be... by Anonymous Coward · · Score: 0

      If anybody is unsure of what the term FUD means, you can't find a more perfect example than this.

    85. Re:Well I'll be... by X0563511 · · Score: 1

      what they can do is sign another piece of secret claiming to belong to you, which is highly visible and obvious.

      How so? If you trust them (why bother having them sign if not?) then you would trust the replacement.

      Unless you check the KSN or fingerprint every time you establish a connection to be sure it hasn't changed?

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    86. Re:Well I'll be... by X0563511 · · Score: 1

      So you're saying the OEMs can install the keys, but the end-users can't?

      We're talking about folks installing Linux - if they could, they would have no problem installing their own keys.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    87. Re:Well I'll be... by X0563511 · · Score: 1

      It's a shim, you probably don't even have to go that far. Think grub legacy - once the stage is loaded and running, it can chainload to anything else.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    88. Re:Well I'll be... by bluefoxlucid · · Score: 1

      Typically, keys are cached when retrieved. When you re-obtain them, and they change, you get notified; or at least a log is kept. Some people are nosy and verify this. Unless you're being targeted very, very specifically... yeah. Not only that, but such fuckery creates evidence which persists, so there is a risk of being caught--which will happen eventually, and once you've done it once people will distrust you forever.

    89. Re:Well I'll be... by Bengie · · Score: 1

      Name and shame your mobo manufacturer. Disabling securboot is part of the UEFI standard is is required to be Win8 compatible. You could technically claim that your mobo does not support Win8 nor UEFI.

    90. Re:Well I'll be... by EvanED · · Score: 1

      I'm not sure why this was modded troll.

      If you want to argue that boot viruses are likely to ever be much of a problem, that's fine. If you want to argue that secure boot is the wrong solution, that's also fine. Both would be an interesting discussion.

      But saying "it's not currently a problem so MS shouldn't do anything about it"? That's dumb, and what I was trying to call out.

    91. Re:Well I'll be... by tepples · · Score: 1

      You can install your own keys.

      Only on x86. It's the exact opposite on ARM.

    92. Re:Well I'll be... by tepples · · Score: 1

      Another way to lose Windows Certification is not allowing the end user to disable Secure Boot.

      And another way to lose Windows RT Certification is allowing the end user to disable Secure Boot.

    93. Re:Well I'll be... by Anonymous Coward · · Score: 0

      Finally, a person that sees this for what it really is, another DRM lockdown. Clap, Clap, Clap and not meant being sarcastically either.
      Search web cam spy patents and/or microsoft kinect spying on you. The buisness model outlines a Pay Per Use Goal for the media industry.

  2. Why not promote motherboard manufacturers by future+assassin · · Score: 1, Interesting

    who dont have or build motherboards that can disable EUFI. Seems to me like there's a great market for non EUFI mother boards that can target Linux/Unix users.

    --
    by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
    1. Re:Why not promote motherboard manufacturers by kthreadd · · Score: 1

      Well you can just turn the feature off, if your board has it and it happens to be turned on.

    2. Re:Why not promote motherboard manufacturers by Tyr07 · · Score: 1

      Linux is often blessed with security when properly setup. Continuing on that path involves being part of UEFI. The reason they want it to be signed is so they can operate on secure systems that do not allow access to the bios to simply disable UEFI and boot any OS on that system.

      Conceptually would be for secure locations that normal PC access is restricted, and do not want uncontrolled software booted to bypass their existing OS security, gaining access to the network and so fourth.
      It's more obvious if someone tried to sneak in a PC versus a bootable USB key. (Yes I know there's some very small ones, but please, stick with the conceptualized idea)

    3. Re:Why not promote motherboard manufacturers by Arker · · Score: 5, Interesting

      It's UEFI, the Unified Extensible Firmware interface. EUFI is ExtraUterine Fetal Incubation. Very different things.

      The motherboards they are shipping now have a simple disable. So there is no immediate fear of being unable to run Linux on the things. BUT you have to go in and disable it in BIOS which is just completely over the head of most computer users these days. You dont have to make it impossible to deter most people from using it, just a tiny hurdle will divert the herd.

      Right now they are signing the certificates without a problem. But what will they do in a year or five or a decade? Building a business that relies on getting certs signed by MS doesnt seem wise long term. Of course no one thinks long term anymore... a small change in the law here, an easily fabricated incident using a signed bootloader to compromise a business there, and they could easily revoke these keys.

      The other problem is that UEFI is actually really cool tech, we dont want to get rid of it. We want to be able to use it. I should be able to install my own key on my own motherboard so it will only load code that I sign personally. Rather than simply trusting MicroSoft or turning off a great security component that I already paid for and theoretically own.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    4. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 5, Insightful

      Conceptually, if the user has access physical access to the computer and the ability to plug shit in, your security is already gone.

      Conceptually, 99.99% of computer users don't even need this kind of security in the first place, so why is it being forced on 100% of the new computers?

      Conceptually UEFI won't stop a single virus which 100% of computer users face daily, and that IS a problem.

      UEFI serves one and only one purpose. It makes it 'easier' to just continue using Windows and more difficult to use any other system.

      Linux doesn't need UEFI. Nobody needs UEFI.

      Stopped shilling lipstick on a pig.

    5. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 1

      UEFI is actually really cool tech, we dont want to get rid of it.

      Yes, yes we do. And once it's gone we want to get rid of all the idiots who thought it was really cool tech so it doesn't happen again.

    6. Re:Why not promote motherboard manufacturers by rmdashrf · · Score: 1

      For now, anyway.

      --
      Nihil in publicum sputa.
    7. Re:Why not promote motherboard manufacturers by lister+king+of+smeg · · Score: 1

      no we want to get ridnof secure boot. uefi lets you boot to a harddrive over 3 Tb in size. I wish coreboot was more developed.

      --
      ---Saying gnome 3 is better than windows 8 not so much a compliment as it is damning with light praise.
    8. Re:Why not promote motherboard manufacturers by gigaherz · · Score: 1

      Let me rewrite that for you:

      No, we want to Secure Boot to be strictly opt-in. UEFI on its own brings many good advantages over the ancient 16-bit BIOS boot process, that we DO want to keep. Just because someone put a lock in it and didn't give you the key doesn't make the existing technology bad.

    9. Re:Why not promote motherboard manufacturers by UltraZelda64 · · Score: 1

      Replace "UEFI" with "Secure Boot" (there is a difference... EFI alone is not a major problem) and I agree 100% with you. While I'm not so sure UEFI is much better than the BIOS aside from a few limits lifted, the real problem is Microsoft's Secure Boot, which is an optional part of UEFI and being forced onto all ARM machines (thanks dicks, I mean Microsoft). Eventually, it will probably make its way to anything else Windows touches with no way to turn it off (x86?).

    10. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 1

      You're not the first one to make that claim. However, none of those making the claim have ever explained how to do so.

      I've tried google. It tells me I need to enter UEFI setup. They don't, however, explain how to do that. I tried F1, F2, ESC, DEL, but no.

      I then tried to google how to enter UEFI setup. Guess what. Everybody explaining how to do that assume that you want to run Windows 8. In Windows 8, it's hidden under shutdown settings in control panel, or something like that.

      So, theoretically you might be able to turn off secure boot, if you've already bought Windows 8, but then why would you want to turn it off?

    11. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      the real problem is Microsoft's Secure Boot, which is an optional part of UEFI and being forced onto all ARM machines

      I didn't know Microsoft had that much control over how Apple and Samsung build their devices!
      Seriously, most ARM based devices have locked bootloaders.
      The only reason Linux supporters have got their knickers in a twist is because they thought Windows on ARM meant they were going to get a number of devices that Linux could be installed on in the same way that it can on PCs.

    12. Re:Why not promote motherboard manufacturers by aaaaaaargh! · · Score: 1

      Conceptually would be for secure locations that normal PC access is restricted, and do not want uncontrolled software booted to bypass their existing OS security, gaining access to the network and so fourth.

      Well, good luck with your rescue CD if it doesn't boot!

      Conceptually, the purpose of secure boot is to keep unwanted operating system software secure from the user (rather than keeping the user safe from malicious software) and preserve a quasi-monopoly for Microsoft. Hopfeully, there will be EU rulings that prohibit current practise.

    13. Re:Why not promote motherboard manufacturers by ldobehardcore · · Score: 1, Informative

      Try all the F# Keys. It might take a while, as they might have set the pause for FKeys to be something braindead stupid like 1/3rd of a second or some bullshit like that. so try all of them: F1 Through F12. If none of them work, and neither Delete nor Escape, nor the Space Bar works, then I gotta say you've wasted your money.

      Although, there might be a jumper on the mobo (literally a couple of prongs bridged with a piece of plastic holding some foil) that you can break and refit that can reset your bios so it'll tell you what buttons to push.

      Also, try unplugging your HDD and see what the error screen says. It may tell you what to hit on startup in order to get to your UEFI/BIOS.

      --
      Hectice, baby, Mercator says hello to you
    14. Re:Why not promote motherboard manufacturers by SuricouRaven · · Score: 4, Informative

      Just to clarify: UEFI is not the problem. It's just a replacement for the old BIOS system which addresses the decades of accumulated legacy bodging that is the PC. Secure Boot is a feature that UEFI enables. You can have UEFI without Secure Boot.

    15. Re:Why not promote motherboard manufacturers by smash · · Score: 1

      No, i'd like to be able to determine what gets to boot on my machine, thanks. i.e., i want secure boot and i want to have the facility to securely install my own keys.

      --
      I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
    16. Re:Why not promote motherboard manufacturers by devent · · Score: 1

      I do. I am not find UEFI a "cool tech". I find UEFI the same as the old BIOS: totally useless.
      When a computer starts it should just bring up the very basic stuff and then handle the boot process to the Operating System. Nothing more. The computer should stay in a state of the BIOS for about 500ms (the quicker the better) after that the Kernel of the System takes over.

      Please tell me what I get with UEFI what the current Linux Kernel does not offer.

      --
      http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
    17. Re:Why not promote motherboard manufacturers by devent · · Score: 1

      Or you can have a BIOS that addresses the decades of accumulated legacy bodging that is the PC, without UEFI.
      Just put a BIOS that removes all the old cruft of the old BIOS, adds some new features, but is totally minimalistic.

      Because in 10 or 20 years UEFI will be like the old BIOS. It will do totally old stuff that nobody wants, and it will not allow new stuff, because of the same reasons of the that the old BIOS have.

      The only remedy is to have a totally minimalistic BIOS that puts control as fast as possible to the System kernel.
      We had "Secure Boot" stuff for Linux for a long time before Secure Boot.
      See:
      https://fedoraproject.org/wiki/Tboot
      http://sourceforge.net/projects/tboot/

      --
      http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
    18. Re:Why not promote motherboard manufacturers by KingMotley · · Score: 2

      Nobody needs UEFI

      That's bullshit. I need UEFI. BIOS only allows a very limited set of space (384K) for hardware device BIOSes. I've hit that limit, as does most server admins because high performance devices use that space up very quickly. There is numerous other advantages to UEFI, but you'd need to take off your tin foil hat and actually learn about it for you to understand it. That or build a server. Then you'll be crying about why stuff doesn't work and how stupid BIOS really is and why there isn't something better out there.

    19. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      except these imaginary mistaken purchases never happened. only the vendetta lives on until paid in MS blood!

    20. Re:Why not promote motherboard manufacturers by Viol8 · · Score: 1

      You already do - via these wonderful programs called Boot Loaders. You should read up about them sometime, you never know, you may even get a clue.

    21. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      IEEE OpenFirmware, look it up.

    22. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      > Just because someone put a lock in it and didn't give you the key doesn't make the existing technology bad.

      Of course it does. There is 100% application of a lock for less than a 1% market use case. That's integrated too tightly. It's bad technology.

    23. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      smash,

        Google - dual boot.

    24. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      First you ask for less, then you want to judge usefulness on what has more.

      First you say that BIOS is totally useless, then explain you want it to do what it already does.

      I do not think you know as much as you think you do.

    25. Re:Why not promote motherboard manufacturers by petermgreen · · Score: 4, Informative

      There is no reason that a traditional PC BIOS can't boot a 3TB drive. The bios just reads the first sector of the drive and runs the code, it doesn't need to care what type of partition table is used. So the 2TB limit of the DOS style partition table is irrelevent to the first stage of booting a PC. AIUI grub2 has no problems being booted by a traditional PC bios and then going on to read a GPT partition table and load linux from it.

      The inability to boot windows on a 3TB GPT drive with a traditional PC bios is entirely microsoft's fault.

      --
      note: i'm known as plugwash most places but i screwd up registering that here somehow in the past and now can't register
    26. Re:Why not promote motherboard manufacturers by gman003 · · Score: 3, Interesting

      Or you can have a BIOS that addresses the decades of accumulated legacy bodging that is the PC, without UEFI.
      Just put a BIOS that removes all the old cruft of the old BIOS, adds some new features, but is totally minimalistic.

      That's what UEFI is - it drops old cruft (mainly ISA, AGP and such, IIRC), ups the minimum requirements (UEFI can assume some level of graphics support, so no more MDA text mode; likewise, it no longer runs in 16-bit mode), and extends functionality (booting off 2TB+ drives). They broke compatibility in a few places, but they did so, in part, to speed up boot times by moving functionality from the BIOS/UEFI to the OS.

      UEFI, itself, is a big step forward. The only problem is the "Secure Boot", and honestly, the problem is currently theoretical (at least on x86 - ARM is a different story). Secure Boot itself is fine - as long as the user is allowed to add and remove keys, and can enable/disable it, it's at worst unneeded functionality.

    27. Re:Why not promote motherboard manufacturers by chihowa · · Score: 1

      Because in 10 or 20 years UEFI will be like the old BIOS. It will do totally old stuff that nobody wants, and it will not allow new stuff, because of the same reasons of the that the old BIOS have.

      Of course that's true, but the E in UEFI is an attempt to make it last as long as possible. I'm not sure what's so objectionable about UEFI, though. It is, essentially, "a BIOS that addresses the decades of accumulated legacy bodging that is the PC."

      --
      If you want a vision of the future, imagine a youtube comments section scrolling - forever.
    28. Re:Why not promote motherboard manufacturers by ak3ldama · · Score: 1

      I do not understand this stuff all that well, but wouldn't it be a problem if _you_ could be the one in control of what the system started out determining as a securely signed key?

      TC is controversial as the hardware is not only secured for its owner, but also secured against its owner.

      If Microsoft wasn't in control of the secure boot key, then wouldn't they have to determine that it is not fully trusted and etc etc? Are you arguing to be able to set your own private endorsement key?

      Anyways I agree that Secure Boot needs to go as it serves no purpose. If it is there it should be disabled by default.

      --
      "but money is the God of Algiers & Mahomet their prophet." - Rich. O'Bryen June 8th 1786
    29. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      "Really cool tech"? In what way? Because I can now use the mouse in the setup screen? I actually vastly prefer the "dangerous, obscure" command prompt of OpenBOOT because, you know, I can actually do interesting things with that. But nnnnoooooooo, dancing rodents!

      That's what spells "really cool tech" these days?

    30. Re:Why not promote motherboard manufacturers by maccodemonkey · · Score: 1

      UEFI serves one and only one purpose. It makes it 'easier' to just continue using Windows and more difficult to use any other system.

      Linux doesn't need UEFI. Nobody needs UEFI.

      Stopped shilling lipstick on a pig.

      UEFI and secure boot are not the same thing.

      I'm sitting at an EFI Mac right now, and have owned a UEFI machine. Neither had secure boot or needed signed copies of an OS. Both the Mac and the Windows box will boot any unsigned OS you throw at it.

    31. Re:Why not promote motherboard manufacturers by bws111 · · Score: 1

      Wait, so the system kernel is magically going to still be functional in 10 or 20 years, but UEFI isn't? What magic makes that happen?

    32. Re:Why not promote motherboard manufacturers by Arker · · Score: 1

      "I do not understand this stuff all that well, but wouldn't it be a problem if _you_ could be the one in control of what the system started out determining as a securely signed key?"

      How on earth do you figure it would be a problem if I was the one that determined what keys my system, that I paid for and own, trusts?

      Really, I am not trying to be dense, I have no clue what you are trying to say here. It's a security system that is part of my hardware. Why would I not be the one to determine what keys it trusts?

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    33. Re:Why not promote motherboard manufacturers by Arker · · Score: 1

      No, I prefer command prompts myself actually. What's really cool about the tech is the bit where it can ensure that the boot loader hasnt been altered before proceeding. A fundamental piece of security that we should have had 20 years ago.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    34. Re:Why not promote motherboard manufacturers by ak3ldama · · Score: 1

      The argument is that it is "Microsoft's" security system* that is part of their ecosystem. I am not trying to say you "shouldn't" (theoretically) have that ability - but under the trusted computing platform isn't there a system of trust that depends on the kind of lock down where the private endorsement key is not set by you? Such that if you did put on your own key Microsoft would no longer want to trust your computer. Someone with more knowledge should weigh in...
      *Also I think MS would probably argue it wouldn't just be their ecosystem but that others could utilize this chained-system of trust.

      --
      "but money is the God of Algiers & Mahomet their prophet." - Rich. O'Bryen June 8th 1786
    35. Re:Why not promote motherboard manufacturers by Arker · · Score: 1

      "The argument is that it is "Microsoft's" security system* that is part of their ecosystem."

      Wait a moment here, I buy commodity hardware, install something *nixy that I compiled and signed on it, and somehow this is part of MicroSofts ecosystem that they have proprietary rights in? Huh?

      "but under the trusted computing platform isn't there a system of trust that depends on the kind of lock down where the private endorsement key is not set by you? Such that if you did put on your own key Microsoft would no longer want to trust your computer. "

      Not asking Microsoft to trust my computer. Why would they?

      This is just a cryptographic verification function to prevent an altered bootloader from executing. My computer doesnt need to trust Microsofts key, and their computers dont need to trust my keys either.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
    36. Re:Why not promote motherboard manufacturers by SuricouRaven · · Score: 1

      The usual issue with change. From the perspective of the users, BIOS works. It's long-established, well-tested and generally very reliable. There are numerous advantages of UEFI to the engineers, but those people not left supporting a mountain of dubious code need to see some advantage to justify the change. What can UEFI do that BIOS cant?

    37. Re:Why not promote motherboard manufacturers by devent · · Score: 1

      Because it is trivial to update the kernel. You install a new system, you get a new kernel. On Fedora a kernel updates every 3 weeks.
      Compare that with the difficulties to update the BIOS. Also a Bug in the kernel will only affect the current system, not the whole computer. I think most people do not update the BIOS at all for the whole lifetime of the computer.

      --
      http://www.mueller-public.de - My site http://www.anr-institute.com/ - Advanced Natural Research Institute
    38. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      That's bullshit. Hardware device BIOSes? Do you seriously even know what a server is?

      Server admins are EXACTLY the people who are getting into the BIOS to turn off that pesky UEFI feature. You know, just like Microsoft 'demands' of OEMS to include to do (for now)? The fact that it can (for now) be optionally disabled in the BIOS is the only thing that lets you build servers in the first place.

      So go crying back to your Windows Server Admin cocoon.

    39. Re:Why not promote motherboard manufacturers by evilviper · · Score: 2

      UEFI can assume some level of graphics support, so no more MDA text mode

      No it can't. Servers will still be restricted to text mode, because out-of-band management is commonly through IPMIv2, which supports text only, not graphics.

      It's ironic that Microsoft is getting on-board with text-mode OS for their servers, while at the same time, Linux distros are going the wrong way and forcing GUI installers, using a pointless graphical splash screen for the bootloader, and other nonsense that helps no-one, but screws up serial and IPMI consoles.

      and extends functionality (booting off 2TB+ drives).

      Nope, I've been booting 2TB+ drive arrays for many years, with plain 16-bit BIOSes.

      UEFI, itself, is a big step forward

      Compared to the legacy BIOS, yes (though it comes with plenty of steps backwards, as well), but it's a big step backwards compared to every other firmware out there: LinuxBIOS/coreboot, OpenFirmware/OpenBoot, SRM firmware, etc. Just about ANYTHING out there would have been better than Intel's bloated UEFI.

      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    40. Re:Why not promote motherboard manufacturers by bws111 · · Score: 1

      You obviously have no idea whatsoever what you are talking about. Yes, hardware devices have BIOSes. What do you think puts out all those messages when a server is booted (before the OS is loaded)?

      You can't 'turn off' UEFI, and you certainly can't do it in the BIOS. UEFI replaces BIOS. Yes, there may be an option (in UEFI) to make UEFI act like BIOS (for operating systems that can't support UEFI), but it is still UEFI, not BIOS.

      UEFI is not Secure Boot, and Secure Boot is not UEFI.

    41. Re:Why not promote motherboard manufacturers by X0563511 · · Score: 1

      I'm pretty sure he is bitching about Secure Boot, not UEFI itself.

      --
      For large sets, this will be our guide even unto death, for the LORD will work for each type of data it is applied to...
    42. Re:Why not promote motherboard manufacturers by bws111 · · Score: 1

      I don't think you have any idea what UEFI actually is or does. SOMETHING has to initialize adapters. What do you propose this to be, the kernel? How does the kernel get booted when the system doesn't even know the disk drive exists, and the drive controller has not yet been intialized? SOMETHING has to have an inventory of what devices there are. SOMETHING has to maintain the RTC. SOMETHING has to provide access to NVRAM. How is the kernel supposed to do those things?

      The purpose of UEFI is to provide standard methods of doing those things, so that the kernel doesn't have to know about every possible configuration that any manufacturer could come up with.

      BIOS used to be what did those things, but it is getting harder and harder to evolve BIOS to do what today's machines need. UEFI is the fix for that. Your proposal (everything in the kernel) would take us back to the nightmare of early DOS.

    43. Re:Why not promote motherboard manufacturers by Darinbob · · Score: 1

      Why are these devices using BIOS? You should only need that to boot up, and once booted never use BIOS until the next boot. BIOS has been updated over the years but is still very archaic and needs updating. Secure Boot is a separate issue.

    44. Re:Why not promote motherboard manufacturers by KingMotley · · Score: 1

      Mostly boot devices, or devices that need BIOS support or extended BIOS support (large drives, 4k drives, etc) mainly, there is also issues with the amount of space available for memory mapping devices, used for high speed I/O controllers, video cards, things that do DMA transfers, etc.

    45. Re:Why not promote motherboard manufacturers by Bengie · · Score: 1

      Theoretically, Secure Boot allows one to protect a computer from undetected modification when someone has gain physical access to said computer. It also can keep malware from modifying any part of the boot process.

    46. Re:Why not promote motherboard manufacturers by Bengie · · Score: 1

      Trying to find some name brand motherboards that have this.

    47. Re:Why not promote motherboard manufacturers by Darinbob · · Score: 1

      But don't most modern systems completely ignore BIOS once booted? Let the OS do the work. I can see the need during boot up, because the OS is not running yet or even started. Once you've got some real code loaded and access to files, then dump BIOS and start loading real device drivers instead. Does BIOS restrict your memory mapped space even once you've ejected it from the OS? What does Linux do with these devices?

    48. Re:Why not promote motherboard manufacturers by KingMotley · · Score: 1

      Linux will have the same issues, it's not OS related. I found out the hard way, and there are tons of messages on the boards of high performance controllers and the like about finding motherboards that have the highest amount of free option ROM space so that the devices can even initialize far enough to get the OS up and running. It's part of the reason why server BIOSes and motherboards are typically pretty bare bones. Almost all devices require some option ROM space so they can initialize themselves, and if you have lots of things on the motherboard (Sound, USB controllers, storage controllers, RAID, etc), there is little space left for expansion.

      In my case I had two controllers I wanted to use in addition to my motherboard's. I couldn't even get one of them to work at all unless I flashed with an older (buggy) BIOS that used just slightly less space, just enough to fit that controller's option ROM. There definitely wasn't nearly enough space for both of them, nor if I wanted another. For example, the OCZ Revo 3 x2 card, and an megaraid 9860 card. I was using these in addition to the intel raid on the motherboard. There simply isn't a single non-UEFI motherboard that has enough room, and only a select few that could even be used with the OCZ Revo 3 x2 by itself. Changing my motherboard to a UEFI motherboard resolved all the issues and I could use all 3 raid controllers with no problem. The BIOS based ones would refuse to boot at all, or one of the devices wouldn't work at all even after going into the OS. I don't think the OS can make more space available for the ROMs and without them, the devices don't work. Nor is there a way to initialize them since there isn't a place to map it's memory. I'm not an expert on it, all I know is that is what the experts described to be, and sure enough the very first UEFI motherboard had no issues at all.

    49. Re:Why not promote motherboard manufacturers by Darinbob · · Score: 1

      PCs are just wierdly designed things. They were designed by accretion over time by companies all trying to get one tiny incremental improvement over the competition, rather than sitting down and figuring out the right way to do things. The fact that there's option ROM in the first place is a work around for lack of good device capability querying during boot in the early days, and some cards actually have x86 code in them and thus not usable with different CPUs. Compare to Open Firmware where devices that do have this sort of firmware on the card themselves does it in a platform independent way.

      I've bumped into problems in the past with PCI devices plugged into non-PCs and all official documentation for the device basically says to let the BIOS do the work for you for some operations.

    50. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      Wait a moment here, I buy commodity hardware, install something *nixy that I compiled and signed on it, and somehow this is part of MicroSofts ecosystem that they have proprietary rights in? Huh?

      To quote...

      The vendor of a TPM-enabled system has complete control over what software does and does not run on the owner's system.

    51. Re:Why not promote motherboard manufacturers by Tyr07 · · Score: 1

      I didn't mention anything about keeping the 'user' safe from malicious software.

      I'm thinking more along the lines a malicious user booting up an a custom quick loading OS to maybe copy files off of a machine or other such purpose. It does happen.Scenario - You want to copy files of a game or movie in production. The system is normally locked down, you don't want to get caught, USB ports are disabled for file transferring, internet traffic is monitored. What do you do? You don't have admin rights, and you don't want it logged.

      You pop in your USB stick and boot off of it, or a CD. If this is disabled, one could if the case is not sealed, swap the HDD cable with their own and place the primary has a secondary HDD.
      You're now able to boot in, copy the information, undo what you've done, and none is the wiser.

      You obviously don't want to be busted so you can't reset the bios, as you can't reconfigure the password etc. Turning off UEFI won't be an option, so a plan like that would be foiled if they OS had to be signed.

      If I can think of it, many others can.

    52. Re:Why not promote motherboard manufacturers by amoreperfectvacuum · · Score: 1

      EFI or something like it really is necessary at some point. Real mode must go away, and BIOS depends on real mode. Intel processors can't go on pretending to be supercharged 8086's forever. EFI allows much more evidently as well. A whole operating system can be crammed into it for embedded systems, or phones and tablets. I was very worried when I bought a laptop recently and realized that I would need to do a EFI install, since it seemed bricking would be a real possibility, but the current generation of Ubuntu LTS worked completely painlessly. So I would say the basic linux shim method is a painless klug for the moment from the user perspective.

    53. Re:Why not promote motherboard manufacturers by countach · · Score: 1

      I'm not convinced. I don't want any random spyware / malware / virus to be able to install a bootable image into my computer. I want the ability to install an OS type image to be restricted at the hardware level for security. This is what secure boot does. It's a good thing.

    54. Re:Why not promote motherboard manufacturers by Anonymous Coward · · Score: 0

      If Oracle is brand name enough for you, then SPARC boards have it. Otherwise, find a G5 PowerMac.

  3. haven't by marienf · · Score: 1

    What we need is boards that are user-rekeyable. That way we can insure that our boards will never run Windows again.

    1. Re:haven't by kthreadd · · Score: 1

      Absolutely and that's how secure boot is supposed to work all along. Anything else is a bug.

    2. Re:haven't by Anonymous Coward · · Score: 0

      Something tells me that Apple won't ship machines locked to Microsoft. This could be a serious uprise for them in the GNU/Linux market.

    3. Re:haven't by DrSkwid · · Score: 1

      I can sell you such insurance if you like.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    4. Re:haven't by SuricouRaven · · Score: 1

      No, they'll just ship machines carrying both the Microsoft and their own key. Apple are no fans of linux - just look at all the hoops you have to jump through to get it running on the new retina macbook pro. They've never officially supported it, and there's no reason they would.

      In the PC area, Apple are dependant upon OSX to be their identity and differentiator. Without OSX, they are just another maker of high-end PCs - and it'd be very hard to sell Apple PCs if they were interchangeable with the one-third-the-price offerings from Dell.

    5. Re:haven't by aaaaaaargh! · · Score: 5, Insightful

      Absolutely. Both Apple and Microsoft have long recognized that free operating systems are the biggest threat to their business models. Operating systems do not offer enough ways to stay ahead of competition by innovation, once the basic needs are fulfilled new features become mere gimmicks that might be nice to have but are not essential (see history of OS X).

      Both Apple and Microsoft have a well-recorded history of anti-competitive business behavior and have in the past tried by all means to keep the application barrier up. In the 90s Java and Web-browsers were the biggest threats and they successfully averted these by tricky anti-competitive behavior. SCO tried to sue free operating systems out of existence and failed (so far, bogus patent law can change that and new law suits are in the drawer), now GNU/Linux has matured so well that it has become intolerable to Microsoft and Apple. Bear in mind that you can run many Windows programs in Wine already and that GNU/Linux has reached a certain usability threshold putting it roughly on a par with Windows XP in terms of software that end-consumers actually need (and GNU/Linux is much more stable).

      The sole and only purpose of the current secure boot specification is to be the entry ticket to completely locked-down machines with completely locked-down whitelisted software that is only runnable and distributable by obtaining a key from Microsoft or Apple respectively and only with their blessings. That's the long-term goal.

      The current, more modest goal is to make it hard for end-users to install another OS and hard to set up dual boot systems. Microsoft will then urge (=blackmail) hardware makers to produce more consumer boards that can run only Windows, and Apple will start to make their manufacturers produce OSX-only boards, while at the meantime urging manufacturers to sell more expensive motherboards that are not locked down so they can still claim they allow competition. For Microsoft, this is particularly important, because they need to make money with Windows and the "windows tax" is annoying more and more people. So they want to make sure that a board that runs GNU/Linux or BSD systems is more expensive (a 'pro feature', so to say) than a consumer board that only runs Windows plus the OEM fee for Windows. Microsoft is very desperate to keep their huge share of the dwindling desktop market, because they have already lost the mobile market.

      This might all sound exaggerated to you now, but the fact is that these companies plan far more ahead than some people might think.

    6. Re:haven't by MrNemesis · · Score: 1

      This might all sound exaggerated to you now, but the fact is that these companies plan far more ahead than some people might think.

      When certain geeks saw the long-term implications for Microsoft's "Palladium" technology ten years ago, they were often laughed at for being overly paranoid and assured that such a thing could never and would never happen. There's no way to lock down a computer like that since we'll always be able to remove the TPM or bypass the BIOS, and not even Microsoft would be stupid enough to produce an operating system that would only boot on "authorised" hardware! Right?

      http://en.wikipedia.org/wiki/Next-Generation_Secure_Computing_Base

      The concept is alive and well and if people think that MS won't tighten the thumbscrews if margins get squeezed then I've got a rose-tinted bridge to sell them.

      /From my parent's home in Wyoming, I stab at thee!

      --
      Moderation Total: -1 Troll, +3 Goat
    7. Re:haven't by Anonymous Coward · · Score: 0

      Citation for your claims about Apple, please? Apple is a hardware company. Why would they want to prevent you from installing Linux if it means potentially less hardware sales?

    8. Re:haven't by jbolden · · Score: 1

      I think you are wrong. Apple likes their machines to be able to boot Microsoft OSes it is a selling point for them. So Microsoft will be one of the keys installed. They might pay the $99 to get their OSX versions signed or have their own key.

      The FSF should just create a key and start signing distributions.

    9. Re:haven't by jbolden · · Score: 1

      just look at all the hoops you have to jump through to get it running on the new retina macbook pro.

      That's not Apple's fault. They aren't doing anything unusual. That's the fault of Linux for not keeping up with spec hardware.

    10. Re:haven't by jbolden · · Score: 1

      I'm not sure what you are talking about. At the time when Palladium was in the Longhorn pipeline the whole goal was that features wouldn't effectively boot without being part of the locked down operating system. So the OS would boot but the DRM subsystem wouldn't work on actual content. Effectively this was policy.
         

    11. Re:haven't by SuricouRaven · · Score: 1

      The idea is basically the same: Chain of trust. The firmware only loads signed bootloaders, the bootloader only loads signed OSs, the OS only loads signed drivers. The difference is just in the response to unsigned code: Secure Boot simply refused to load it, while the Palladium/NGSCB would load the code but set a 'don't trust this' flag which a trusted store could use to verify system integrity. So while you could install an unauthorised OS or drivers on a NGSCB computer, your DVD/blu-ray drive would disable itsself, your secure cryptographic locker would refuse to open and you wouldn't have a hope of getting your legitimately paid-for downloaded movies and music to play.

      Pirate media would, of course, play without a problem.

    12. Re:haven't by SuricouRaven · · Score: 1

      Apple isn't just a hardware company. Hardware is just one aspect of a larger business. They make PCs and laptops, but they also make consumer electronics - media players and smartphones. They run a successful media store, too. One of their big successes is tying all this together into an ecosystem, so every product serves to promote all the others.

      Someone who buys a mac and runs linux brings Apple money, but not as much as someone who bought the mac and started utilising the app store and itunes media store, which in turn would push them towards buying an iPad and iPhone.

    13. Re:haven't by ducomputergeek · · Score: 1

      I've heard this dreck for well over a decade now. Right up there with "year of desktop Linux" which really has never happened. Linux was never a threat to Microsoft and windows on the desktop. Linux killed the Unix venders.

      Linux is not a threat to apple. Hell apple now maintains some key components that Linux widely uses (ever check and sees who owns and maintains CUPS these days).

      And Linux is not dominating the mobile market. While android may use Linux underneath, when people by a droid phone, they think google and android os.

      What keeps people like me using macs and windows are two factors. Ironically the same two factors to why I switched to osx over 10 years ago.

      1) Lack of major software packages. For better or worse the business world runs on office. Personally at home I can get away with using OpenOffice or iWork. But for work, I've tried and always end up having to use office for some reason.

      2) lack of quality hardware - on the server side Linux has this, not so much on the desktop and laptop side. Even windows now have this problem. I buy MacBook pros because I have yet to have one that has lasted under 4 years. Think pads used to have this level of quality, which you also paid for, but over the past 18 months I know a lot of people we work with are complaining that they are on their second or third think pad in that time.

      Maybe as we get more cloud based apps this will change. I'm finding office 360 and skydive increasingly handy as I can now edit office docs online with either an iPad or android tablet easily. But seriously, Linux is still not a threat to either company.

      --
      "The problem with socialism is eventually you run out of other people's money" - Thatcher.
    14. Re:haven't by jbolden · · Score: 1

      Exactly. The Palladium model was better in that it had isolation. You could run untrusted and the trusted part didn't have to care. This is very much like what Blackberry Balance allows for.

  4. Hmm... by Mirar · · Score: 2

    ...what is the point of secure boot again? Do we still have problems with MBR viruses?

    1. Re:Hmm... by Anonymous Coward · · Score: 0

      Yes, there are even a few botnets components out there that patch BIOS level calls nowadays.

    2. Re:Hmm... by rmdashrf · · Score: 5, Informative

      And that attack vector can completely be negated by having the BIOS read-only by default, while only enabling updates when the user toggles a physical switch when the BIOS needs an update.

      --
      Nihil in publicum sputa.
    3. Re:Hmm... by SuricouRaven · · Score: 1

      It's supposed to be a protection against bootloader-infecting rootkits. No-one questions that it can do this, but bootloader-infecting rootkits are incredibly rare things to encounter, and given Microsoft's long history of anticompetative business tactics it isn't hard to imagine their ulterior motive for pushing the technology.

    4. Re:Hmm... by Anonymous Coward · · Score: 1

      It wont protect it against SIGNED and AUTHORISED root kits.

    5. Re:Hmm... by Rockoon · · Score: 1

      And that attack vector can completely be negated by having the BIOS read-only by default, while only enabling updates when the user toggles a physical switch when the BIOS needs an update.

      ...but isnt the only current valid argument against Secure Boot that "its hard for the average user to either disable it or change keys in a bios setup screen, so its a barrier against them installing Linux/BSD/etc"

      ..the upshot of this is that the same excuse can be used to undermine the completely logical argument that you have just made, that not only should there be a Secure Boot, but also that nothing shouldnt be able to alter its settings without the user throwing a physical switch...

      At the end of the day it IS a barrier to entry into alternative OS's for the casual user, but the validity of this argument doesnt actually negate the benefits of Secure Boot, nor does it address the current reality that more and more often the casual user is buying completely locked down devices that can't ever run Windows....

      --
      "His name was James Damore."
    6. Re:Hmm... by KingMotley · · Score: 1

      The BIOS calls are intercepted by a little program that gets run off your media device (USB, Hard Disk, CD-ROM, whatever). Setting the BIOS to read only doesn't defeat that.

    7. Re:Hmm... by Anonymous Coward · · Score: 0

      Hi Sony!

    8. Re:Hmm... by Anonymous Coward · · Score: 0

      and how do you run your media device if you're only allowed to boot into a media with a signed OS? time to turn in your geekcard

      see every bootloader locked android phone for a wonderful example on how this works.

  5. Windows has been using BSD code for over a decade. by Sadsfae · · Score: 1

    Signing their key is the least Microsoft can do for using large parts of the FeeBSD TCP/IP stack in Windows.
    https://lwn.net/Articles/245805/

    --
    Have a squat over at the hobo house.
  6. Loophole by Todd+Knarr · · Score: 4, Interesting

    My bet would be that Microsoft refuses to sign the loader, saying that they can only sign if the loader's coded to only load binaries signed by a trusted authority (ie. Microsoft) and that allowing a loader that can load untrusted (ie. unsigned or not signed by Microsoft) binaries compromises the security of the boot process.

    1. Re:Loophole by Anonymous Coward · · Score: 1

      They're going to do most signings in the start.

      They don't start revoking and closing down their system until everyone uses it. If they refuse FreeBSD now, a lot of people won't go along with this secure boot thing..

    2. Re:Loophole by Anonymous Coward · · Score: 1

      This is what they originally intended, but it does look like such actions would be deemed anti-competitive for very good reasons.

    3. Re:Loophole by Anonymous Coward · · Score: 0

      Yeah, cuz Microsoft has a history of avoiding anti-competitive behaviour, right?

      They have basically tricked the world into giving them an on/ off switch for every computer in the world - they won't use it yet, they will be patient. They have to wait until UEFI motherboards are the norm and most of the older hardware is out of the marketplace. But then they will have the entire planet by the gonads. We're talking James Bond Villain level shit, you really think the threat of a few lawsuits will stop them? They own judges and politicians. OK sure, maybe they'll have to pay a fine or something, but in their view that's more than worth it for (a) a complete OS monopoly on practically all hardware and (b) the power to ransom anybody's PC and data at any time.

      Seriously, fuck Microsoft.

    4. Re:Loophole by gtirloni · · Score: 1

      Just disable UEFI in your motherboard's BIOS and chill out.

      --
      none
    5. Re:Loophole by AmiMoJo · · Score: 1

      It doesn't work that way. Canonical's shim is signed with Microsoft's key but will only load a Linux kernel signed by Canonical with full boot-time privileges. If the kernel is unsigned it doesn't get access to some UEFI features, they are disabled before starting it. This prevents people from writing "kernels" that are just rootkits which load the Windows 8 kernel up afterwards.

      So in fact Microsoft has already signed a shim that can load untrusted code, but on the condition that it does it in a safe way that prevents it being abused by rootkits.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    6. Re:Loophole by Anonymous Coward · · Score: 0

      The your pc wouldn't work. since uefi is the replacement for bios...

    7. Re:Loophole by bluefoxlucid · · Score: 1

      But you can use any initrd. So your kernel loads, loads up the initrd, which kexec -l myshit, and kexecs your rootkit.

    8. Re:Loophole by jonwil · · Score: 1

      With the shim written by Canonical, it will load both signed and unsigned binaries but only signed binaries get access to important UEFI boot-time-only features. And part of the rules for getting such things signed is a requirement that the signed binary must toggle the UEFI disable flag (or whatever it is that disables access to these boot-time-only features) before it hands control over to unsigned code. So by the time your initrd and kexec are running, you no longer have access to these boot-time-only features (which presumably prevents you from loading a virus that in turn loads Windows 8)

    9. Re:Loophole by AmiMoJo · · Score: 1

      If installed on an UEFI BIOS with Secure Boot then Windows 8 won't start unless the BIOS hands over to it, including a cryptographic verification. The whole point of Secure Boot is to prevent rootkits doing what you suggest.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    10. Re:Loophole by bluefoxlucid · · Score: 1

      Why can't the rootkit modify the Windows kernel? The point is that the UEFI knows it's handing over to something secure; if you can hand over to a shim, which then hands over to a kernel which sets up a kexec, which loads a modified kernel (Windows, Linux, OSX, BSD), which doesn't check if it got securely started, then... what?

  7. Why bother re-signing? by Meneth · · Score: 1

    Can't they just use the already-signed blob?

    1. Re:Why bother re-signing? by SuricouRaven · · Score: 1

      Microsoft won't sign a blob that can simply load any kernal, because doing so would defeat the purpose of Secure Boot: An attacker could simply load the linux signed loader with their malicious rootkit and use that.

  8. Re:it already does by kthreadd · · Score: 2

    Apple uses parts of the FreeBSD user land in OS X, and actual parts that works with the hardware and UEFI is not related to it.

  9. Re:Windows has been using BSD code for over a deca by gavron · · Score: 5, Insightful

    MS has the LICENSE to use BSD code.

    They don't owe BSD anything.

    Next time you're thinking of whether to license YOUR code using GPL or using something
    that allows MS to use your stuff and give nothing back in return... remember this.

    Ehud

  10. needs a new installer..still by ThorGod · · Score: 2

    I've tried both the newest PC-BSD and bsdinstall installers...and they leave a lot to be desired. :/

    --
    PS: I don't reply to ACs.
    1. Re:needs a new installer..still by Anonymous Coward · · Score: 1

      No. Just no.

      The installers are fine.

      They work on practically every system out there. They install the system. What more do you want? If you need more flexibility then they provide, it's trivial to write your own install script. Unlike most other modern day operating systems, BSD is structured enough that you can wrap your head around the distribution layout in an afternoon.

      We do not need some gigantic multi-lingual monster that only works under X.org off a live CD. You can leave that shit to the Linux folks, and if you want to know how that's working out for them just ask all the people who had to deal with the installer Fedora is now shipping with (because some idiots said "Hey, our current installer works just fine, let's replace it!").

    2. Re:needs a new installer..still by Anonymous Coward · · Score: 0

      Quote "If you need more flexibility then they provide, it's trivial to write your own install script."

      I need more flexibility, what do they provide?

    3. Re:needs a new installer..still by Anonymous Coward · · Score: 0

      > They work on practically every system out there. They install the system.

      For you to actually use one without 10 years of scar tissue using older versions.

      They were designed by text monkeys. They are *almost* as bad as the new Fedora installer.

    4. Re:needs a new installer..still by Anonymous Coward · · Score: 1

      Oh noes, no pretty graphics :[

      Grow a pair.

    5. Re:needs a new installer..still by ThorGod · · Score: 1

      For one, I wish they handled 4k drives better. Last time I installed zfs on a 4k drive it was a nightmare configuration mess. That particular task should be second nature.

      --
      PS: I don't reply to ACs.
  11. Re:Windows has been using BSD code for over a deca by Anonymous Coward · · Score: 0

    Why would they give back? You can't fix something that is already perfect.

  12. Re:why bother? by Chrisq · · Score: 0

    Surely both people who still run BSD on the desktop could just buy another machine

    They could in theory, but they can't agree on the definition of "open hardware" and are unlikely to resolve this in the near future.

  13. okay, never again run Windows *or* OSX by marienf · · Score: 1

    Don't know where you got the impression that I was somehow favouring Apple hardware, but I stand corrected nevertheless: I should have written "never run any non-free OS, or any code made by someone not truly supporting freedom, in the end".

  14. Useless EFI by Anonymous Coward · · Score: 0

    I don't see much of a problem - it only affects people who wants to dual boot and that is totally last century. Boot Linux and run Windows in a VM.

    1. Re:Useless EFI by nukenerd · · Score: 4, Insightful

      I don't see much of a problem - it only affects people who wants to dual boot and that is totally last century. Boot Linux and run Windows in a VM.

      It is not to do with dual boot, it is to do with booting anything at all. This is a motherboard chip feature. Booting from a live CD will be impossible, and even if you wipe your HD, trying to install anything else will be impossible - if Secure Boot is enabled.

      You can disable Secure Boot (FTTB, but I suspect MS will hope to clobber even that in the not too distant future), and I will myself. But it will deter people from trying out Linux tentatively and perhaps liking it. That's how I started, and MS hate people doing that.

    2. Re:Useless EFI by Anonymous Coward · · Score: 0

      I try to install Ubuntu 1304 versions onto my W8 laptop.
      Ubuntu with Unity installs.
      Ubuntu-Gnome installs.
      Lubuntu fails to put grub.
      Xubuntu fails to put grub.
      And I prefer the later two version.

      Peter

  15. Re:Windows has been using BSD code for over a deca by Anonymous Coward · · Score: 0

    I think OP was talking about an ethical or moral choice.
    You're talking about legal dept.
    Huge difference.

  16. pardon me but the shim.. by gl4ss · · Score: 1

    pardon me but, can't you pretty much boot anything with the shim? thus defeating the purpose.

    from what I can see freebsd could just use the linux shim as well. which is what makes i a shim, that there is no necessity to sign with microsoft everything you boot.

    http://mjg59.dreamwidth.org/20303.html

    --
    world was created 5 seconds before this post as it is.
  17. Re:Windows has been using BSD code for over a deca by SuricouRaven · · Score: 1

    Social conventions like owed favors do not exist in the world of business. When billions of dollars are at stake, there is no room to be 'nice.' That's why contracts were invented.

  18. Microsoft Linux by Anonymous Coward · · Score: 0

    Microsoft Linux is the new name for their Xenix OS.

    Linux lost the battle.

    Roll over doggie.

  19. Re:Windows has been using BSD code for over a deca by KingMotley · · Score: 1

    Windows doesn't use any of the FreeBSD TCP/IP stack anymore. It did at one time pre-Windows XP, but it was completely rewritten from the ground up prior to Windows XP, but many of the settings (registry settings) remained the same for compatibility.

  20. Re:Windows has been using BSD code for over a deca by KingMotley · · Score: 1

    Sorry, I just double checked, it was rewritten for Windows NT 3.5, and then carried over to Windows 95. So the FreeBSD stack hasn't been in use for nearly 10 years. Some of the ancillary utilities however, were never rewritten for some time and might have used some FreeBSD code in them. They carried the "Some parts... blah blah...Berkely... blah blah" messages in them.

  21. Those boot loaders need to be signed. by Anonymous Coward · · Score: 0

    And the only one allowed to sign it is the motherboard maker. And the only one the MB maker will allow to sign is Microsoft. And Microsoft already demand that secure boot be mandatory on (therefore no other bootloader cannot be used) for ARM machines and "the manfacturer is allowed to decide" on x86 *at the moment*.

    Therefore your response was ineed a response. It was not, however, an answer.

    1. Re:Those boot loaders need to be signed. by Viol8 · · Score: 1

      The parent said he wanted secure boot to be able to decide what boots on his machine. My point was you don't need secure boot to be able to do that. He's obviously drunk the MS kool aid. You however should learn to read.

    2. Re:Those boot loaders need to be signed. by Arker · · Score: 1

      Security isnt a binary option. Good security is made with layers. UEFI boot, as long as I have the key to control it, would make a mighty fine layer.

      --
      =-=-=-=-=-=-=-=-=-=-=-=-=-=-
      Friends don't let friends enable ecmascript.
  22. Also giving microsoft a super-superuser account. by Anonymous Coward · · Score: 0

    Since the BIOS already supremely trusts that MS cert, even if you have a hosted virtual machine at the bare metal level, microsoft still have a deeper access to your system compared to you or that OS.

    Why is that a good thing?

  23. Re:Windows has been using BSD code for over a deca by dfghjk · · Score: 2

    You assume BSD is unhappy with this result. They are not...and the problem isn't MS using BSD's "stuff" and not giving anything back to BSD in return, it's not giving anything to YOU in return. BSD got precisely what they wanted in that transaction, you didn't.

  24. Surface Pro and Secure Boot by magamiako1 · · Score: 1

    For what it's worth, Surface Pro (A Microsoft-built device) allows you to disable Secure Boot support if you so choose.

    UEFI -> Secure Boot -> Measured Boot (requires TPM)

  25. Re:Windows has been using BSD code for over a deca by Anonymous Coward · · Score: 0

    Which proves RMS right once again. Copyleft really is a more ethical choice.

  26. Re:HAPPY 4th OF JULY CANADA !! by Anonymous Coward · · Score: 0

    Hey, AC, time to brush up on your history knowledge. You're three decades late. As for Québec, no matter what some people say, we're still currently part of Canada and have been for a long time. Our origins have roots in France but we're not under their authority.

    All Canadians must obey the great robotic overlord Harper or perish under his dictatorship.

  27. NSA - no comments on the MS + NSA yet? by bussdriver · · Score: 1

    NSA - no comments on MS working with the NSA yet?

  28. Microsoft Windows is the most secure OS. by ikhider · · Score: 1

    The Microsoft OS is the most secure operating system. It has never been compromised. Microsoft constantly sets the bar in security, stability, and user flexibility. Secure boot is another precedent, in a long history of security, of how Microsoft works in the interest of the end user. No entity can use secure boot to compromise the Microsoft OS. Trust Microsoft to do the right thing.

    --
    "SO we bide our time, waiting for a purer kick to bloom and the future is still bleak, uncertain and beautiful" -GSYBE
    1. Re:Microsoft Windows is the most secure OS. by Anonymous Coward · · Score: 0

      Thanks for the laugh. I have to go disinfect some Linux PCs ;)

    2. Re:Microsoft Windows is the most secure OS. by iggymanz · · Score: 1

      of more importance in the enterprise is the robustness of microsoft exchange and IIS, which have never passed malware to or from any PC.

  29. Umm, there are native Linux OS machines by ikhider · · Score: 1

    System 76, Think Penguin...I think Dell and HP may still have some native Linux OS machines available. Lemote in China (what Stallman uses) and there are probably more. We don't HAVE to buy a Mac, Asus, Toshiba, or whatever. We look for alternatives and empower them. It is a pity that AMD boards are not in any native Linux OS machine yet. Usually it is Intel that is on this bandwagon. (Are you reading this AMD?) So if you want a non-intel GNU/Linux native board you are stuck with Lemote...pretty much...anyone know better...?

    --
    "SO we bide our time, waiting for a purer kick to bloom and the future is still bleak, uncertain and beautiful" -GSYBE
  30. Re:Windows has been using BSD code for over a deca by Anonymous Coward · · Score: 0

    They should be. At the very least you should be.

    The GPL and similar licenses help protect code from it's creator. An alien concept to many, but an important one.

    To those who disagree: What makes you think you have the right to control the fate of code you've written? Why? Can you provide an argument other than "That's the way it's always been?"

    No code (or any other work) is completely unique. Much of it is largely derivative. The fallacy of copyright provides means to lock public knowledge away from the community.

  31. Fail. by AdamWill · · Score: 1

    "FreeBSD Team Begins Work On Booting On UEFI-Enabled Systems"

    "The FreeBSD project has begun the process of making it possible for the operating system to run alongside Windows 8 on a computer which has secure boot enabled."

    These two things are not the same thing. At all. I am *typing this post* on a UEFI system which has no idea what the hell Secure Boot is.

  32. Re:Windows has been using BSD code for over a deca by bluefoxlucid · · Score: 1

    You mean the choice that other people shouldn't be able to use your stuff without paying you, right?

  33. Re:Windows has been using BSD code for over a deca by evilviper · · Score: 1

    The GPL and similar licenses help protect code from it's creator.

    No it doesn't. An author can change the license at any time, or can simultaneously allow dual-licensing under the GPL and something else. Copyright allows them to do this, and the GPL does nothing to prevent it.

    What makes you think you have the right to control the fate of code you've written? Why?

    Because that's generally the ONLY motivation for me to write any code. If I don't get to chose to sell it, free it, or keep it private as needed, I would never write any non-trivial code. And works for hire would probably almost entirely stop, too, since they can A) Just use the code someone else developed and B) Wouldn't have any way to keep their code secret, or charge a fee to cover development costs.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  34. Re:Windows has been using BSD code for over a deca by evilviper · · Score: 1

    Copyleft really is a more ethical choice.

    There is nothing unethical about allowing others to use your code for free.

    The GPL is no more or less ethical than any proprietary license. It allows people to use your code, ONLY if they meet your terms, and pay you back in the method of your choosing.

    And like proprietary licenses, it's good at keeping companies away from your code, and non-interoperable with the protocols you've come up with to make your life easier.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  35. Re:Windows has been using BSD code for over a deca by evilviper · · Score: 1

    Next time you're thinking of whether to license YOUR code using GPL or using something
    that allows MS to use your stuff and give nothing back in return... remember this.

    Kerberos and LDAP had BSD/MIT licensed implementations, so Microsoft used them, and now Windows systems are far more secure, and authentication is fully interoperable between Windows and Linux/BSD, which wasn't the case before.

    Microsoft using the BSD TCP/IP stack was a GOOD THING. If it was GPL licensed, they would have written their own, probably with bugs and other oddities, and people would have spent years and untold man-hours trying to figure them out, and get the various OSes back to compatibility with each other.

    Maybe if KSH93 was BSD-licensed, Microsoft would have used that, too, instead of developing PowerShell and becoming even more insular, and isolating Windows admins from Unix systems.

    If not for OpenSSH being BSD licensed, we'd all still be using TELNET everywhere, with untold numbers of companies refusing to tie themselves to GPL'd software, and each specific case not being worth the effort to rewrite it in-house, yet the network effects of having a free version that got used everywhere has improved things for everyone who uses the internet. Come to think of it, I'm surprised Microsoft hasn't started including SSH and SFTP with the base system. I suppose that'll come years after it should have, like a defragmenting tool, zip support, jpeg support, MP3 support, etc. etc.

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  36. Re:Windows has been using BSD code for over a deca by Anonymous Coward · · Score: 0

    Are you implying modern windows systems have ssh either as a client or as a server?

    Because as far as I can tell openssh has been around more than a decade, and
    I haven't seen ssh in win2K, 2003, xp, vista. (I've never used 7 or 8)

    m

  37. Then why no GNU/Linux PCs in stores? by tepples · · Score: 1

    If all people want to do on a PC is e-mail, Facebook, and YouTube, then why did Windows netbooks replace GNU/Linux netbooks so quickly? I guess it might have had something to do with Microsoft Office or games.

    1. Re:Then why no GNU/Linux PCs in stores? by RaceProUK · · Score: 1

      That and most customers have no idea what Linux is. For that matter, they don't even know what Windows is, except for 'that thing shown when you turn the computer on'.

      --
      No colour or religion ever stopped the bullet from a gun
  38. Surface Pro is also cost prohibitive by tepples · · Score: 1

    So how long until the Surface Pro or an equivalent tablet becomes price-competitive with the iPad or Surface RT?

  39. BitLocker by tepples · · Score: 1

    At the time when Palladium was in the Longhorn pipeline the whole goal was that features wouldn't effectively boot without being part of the locked down operating system.

    And what came out of the Longhorn pipeline in this case was BitLocker in Windows Vista Ultimate. As I understand it, it's a form of drive encryption that relies on the TPM.

    1. Re:BitLocker by jbolden · · Score: 1

      Right but the goal was much more than just this.

  40. Re:Windows has been using BSD code for over a deca by aestrivex · · Score: 1

    And works for hire would probably almost entirely stop, too, since they can A) Just use the code someone else developed and B) Wouldn't have any way to keep their code secret, or charge a fee to cover development costs.

    Richard Stallman addresses this argument, that if all code were free, what incentive would there be for software developers to exist. He later made the observation -- rightly, I think but certainly open to argument -- that the majority of software development tends to be done for clients that want custom software. This has certainly been true in my experience as a scientific developer (though I am still young).

  41. Re:Windows has been using BSD code for over a deca by evilviper · · Score: 1

    It's true that software development wouldn't stop entirely, it would just be reduced to 0.1% of what it currently is.

    Those clients that want custom software... How happy will they be if to get that custom software, they MUST expose all the proprietary info and trade secrets they put into it?

    --
    Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant