Slashdot Mirror


Microsoft Responds To Linux Concerns Over Windows 8 and UEFI Secure Boot

CSHARP123 writes "A few days ago, Red Hat employee Matthew Garrett speculated that OEM machines shipping with copies of Windows 8 may lock out support for Linux installations. Garrett highlighted Microsoft's new Secure Build OEM requirements for Windows 8 systems. Microsoft chose to directly respond to confusion surrounding Windows 8's use of the UEFI Secure Boot feature on Thursday. Tony Mangefeste of Microsoft's Ecosystem team said, 'Microsoft supports OEMs having the flexibility to decide who manages security certificates and how to allow customers to import and manage those certificates, and manage secured boot. We believe it is important to support this flexibility to the OEMs and to allow our customers to decide how they want to manage their systems.'"

389 comments

  1. Translation by betterunixthanunix · · Score: 4, Insightful

    "Consumers should run Windows, and they should not have any ability to boot up anything else. 'Enterprise' users who can afford to pay more should have more choice."

    That is the only way I can see this playing out. What OEM would not jump at the opportunity to control its users and force people to pay more to do something they have been able to do at no cost all these years?

    --
    Palm trees and 8
    1. Re:Translation by Rich0 · · Score: 1

      Well, more like:

      "Vendors should provide a simple and standard way that lets us get our OS on any PC out there. Others are welcome to come up with vendor-specific hacks or negotiate with every vendor out there as they wish. You see, we're a monopoly so they come to us and we tell them what to do, and good luck competing with that..."

    2. Re:Translation by Anonymous Coward · · Score: 0

      Considering the reaction here; the OEMs that would do this would get so much bad PR, that a significant number of customers would flee to some other manufacturer.

    3. Re:Translation by lseltzer · · Score: 1

      If there's a demand for it some OEMs will satisfy the demand.This is pretty obvious actually.

    4. Re:Translation by icebraining · · Score: 1

      What OEM would not jump at the opportunity to control its users and force people to pay more to do something they have been able to do at no cost all these years?

      Those who don't want to lose business to the ones who don't charge more?

    5. Re:Translation by Anonymous Coward · · Score: 0

      if that actually worked a lot of things would be cheaper already

    6. Re:Translation by Chrisq · · Score: 2

      Considering the reaction here; the OEMs that would do this would get so much bad PR, that a significant number of customers would flee to some other manufacturer.

      The reaction from slashdotters who want to run Linux might not be representative of their market.

    7. Re:Translation by MrHanky · · Score: 1, Flamebait

      Is that so? Practically all OEMs force a Windows license on you, and have done so since forever (1995), as that's more profitable for them. None of them cares whether you actually use it, and I see no reason why they should start now.

      I say you're a shit translator.

    8. Re:Translation by fuzzyfuzzyfungus · · Score: 2

      I'd honestly be more worried about the combination of pressure from Team DRM(sure, we'd be happy to make our "Inspired by Inspiron" new release film collection available for the right price; but look at all the vagabonds on your trusted keys list...) and the general OEM tendency toward a "least effort" model of firmware development, especially; but not exclusively, in consumer hardware.

      There is a long, sordid, history of BIOSes being released that don't even work well enough to keep the spec sheet from being a lie, much less well enough to make using all the features actually safe and stable. Unless some sort of earthshattering magic happens, I'm guessing that UEFI development will go pretty much the same way. Since the product isn't done until Windows runs, Windows will work; but any additional keyfill systems will be a bit of an afterthought, unless specifically marketed as some kind of enterprise feature(in which case they'll be expensive and rather baroque...)

    9. Re:Translation by GordonBX · · Score: 5, Insightful

      Considering the reaction here; the OEMs that would do this would get so much bad PR, that a significant number of customers would flee to some other manufacturer.

      Of course you're right.

      That's exactly what has happened with mobile phones. (cough).

    10. Re:Translation by JamesP · · Score: 5, Insightful

      No, the problem is:

      BIOS vendors are complete idiots

      "EFI" vendors are the same guys

      It's a crapfest of proprietary extensions, NIH syndrome and a million ways to change monitor brightness. And of course it's only tested on the latest Windows version, well, because...

      Of course, Intel is to blame with the whole ACPI mess and looseness. Typical engineer mentality a standard that standardizes nothing.

      Really, Intel and AMD should join forces in this: Make 'to change monitor brightness write a value from 0 (darker) to 0xff (brighter) to register 0xABC PERIOD'. "but but but", "I SAID PERIOD".

      --
      how long until /. fixes commenting on Chrome?
    11. Re:Translation by Anonymous Coward · · Score: 0, Insightful

      It would be the creators of boot loaders who would pay to get their boot loaders signed, not end-users, and the idea would be that it would only be the cost of validation.

      There'd be no reason not to allow people to disable it, if they didn't mind running unsigned boot loaders (just like the TPM module can be disabled if you don't want it), but for the many people who will never have any need to run an unofficial/unsigned boot-loader this will prevent one of the more difficult classes of malware.

      Basically you can think of this as letting companies use signatures for their websites; you need to pay a bit but people can be more confident as a result. Seems pretty reasonable to me (and why are we so eager to hang on to 80's BIOS tech anyway? This is one small part of the UEFI standard which will help keep things flexible, future-compatible, standardized and secure).

    12. Re:Translation by daid303 · · Score: 1

      http://www.computerland.nl/ has been selling machines without OS for years. They have a whole range of machines, just just 1 for the linux guys. They'll assume you pirate windows or install Linux. And they'll happily sell you windows if you ask for it. They also have shops in all parts of the Netherlands, so they are not just some small single location store.

    13. Re:Translation by HJED · · Score: 1

      This would also damage backwards compatibility with older versions of Windows, more likely you will have to change a BIOS setting to turn it off or get annoying messages (such as when you access a website with a self signed SSL cert.) when you try to boot anything other then Windows 8. So it's bad, but not that bad.

      --
      null
    14. Re:Translation by Anonymous Coward · · Score: 0

      5: n=10
      10: We have n standards to do 1 thing, but the standards don't play nice.
      20: We need to make 1 standard for 1 thing, none of the exiting ones fit the bill.
      30: We have n+1 standards to do 1 thing, but the standards don't play nice.
      40: n=n+1
      50: goto 10

    15. Re:Translation by Anonymous Coward · · Score: 1

      Or, more succinctly,the relevant XKCD comic.

    16. Re:Translation by Anonymous Coward · · Score: 0

      Durr. There will be no BIOS. This is all about replacing it with something else.

    17. Re:Translation by SuricouRaven · · Score: 2

      Except that one of the requirements would probably be that the bootloader itsself be incapable of running an unsigned kernal. Otherwise, the system would be trivial to bypass by simply having a signed GRUB load your malware image, and then have the malware image run the real OS. Much like how, for example, console makers will not sign keys for any game designed to be able to load and execute arbitary code, as a signed program with that ability would defeat the point of signing.

    18. Re:Translation by TheRaven64 · · Score: 5, Interesting

      NIH syndrome

      NIH is the reason why UEFI exists at all. OpenFirmware already existed, had several independent implementation (including some open source ones), and was a free standard that anyone could implement. So Intel made a new 'standard' that is a crappy copy of OpenFirmware.

      --
      I am TheRaven on Soylent News
    19. Re:Translation by Anonymous Coward · · Score: 0

      Not true. OEMs circumventing Microsoft desires will soon lose their special Windows licensing deal prices. It's illegal, but MS legals have worked out away around it using different terms, but the net result is identical. No OEM is going to cut into their slim margins to satisfy 0.001% of their customers who want to install Linux or BSD.

    20. Re:Translation by icebraining · · Score: 1

      Depends on the competition. PCs are very cheap already and the manufacturers have very low margins. Seems to be working OK.

    21. Re:Translation by DJRumpy · · Score: 2

      This appears to be strictly feature driven by UEFI, and Win 8 supports this secure 'feature'. This functionality was apparently in UEFI all the time but not supported in Windows. What this appears to saying is that your motherboard (or PC manufacturer as the case may be) will be able to decide just how locked down your EFI is in regards to 'allowed' boot loaders. Windows doesn't have much to do with it other than opting in to that additional security. I'm guessing this was done to try and avoid rootkits?

      From TFA:

      Quick summary
      UEFI allows firmware to implement a security policy
      Secure boot is a UEFI protocol not a Windows 8 feature
      UEFI secure boot is part of Windows 8 secured boot architecture
      Windows 8 utilizes secure boot to ensure that the pre-OS environment is secure
      Secure boot doesn’t “lock out” operating system loaders, but is is a policy that allows firmware to validate authenticity of components
      OEMs have the ability to customize their firmware to meet the needs of their customers by customizing the level of certificate and policy management on their platform
      Microsoft does not mandate or control the settings on PC firmware that control or enable secured boot from any operating system other than Windows

    22. Re:Translation by GameboyRMH · · Score: 2

      I saw it as "We're going to leave it up to the OEMs on what to do, just as we leave the choice of what OSes they sell up to them right now. They'll be completely free to choose whether to maintain exclusivity agreements with us which may require UEFI bootloader signing. See, it's not us, it's the OEMs. ^_^ "

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    23. Re:Translation by diegocg · · Score: 5, Informative

      ACPI was not designed by Intel alone, Microsoft was also there. And let's remember what Microsoft tried to do:

      From: Bill Gates
      Sent: Sunday, January 24, 1999 8:41 AM
      To: Jeff Westorinon; Ben Fathi
      Cc: Carl Stork; Nathan Myhrvold; Eric Rudder
      Subject: ACPI extensions

      One thing I find myself wondering about is whether we shouldn't try and make the "ACPI" extensions somehow Windows specific.

      It seems unfortunate if we do this work and get our partners to do the work and the result is that Linux works great without having to do the work.

      Maybe there is no way to avoid this problem but it does bother me.

      Maybe we could define the APIs so that they work well with NT and not the others even if they are open.

      Or maybe we could patent something related to this.

    24. Re:Translation by Anonymous Coward · · Score: 0

      You have a very odd definition of 'working OK'.

      See IBM, Dell, HP.

    25. Re:Translation by Anonymous Coward · · Score: 0

      Came here to say this, someone mod this guy up.

    26. Re:Translation by DuckDodgers · · Score: 1

      Read up on rootkits. Some rootkits inject themselves into the boot process and get loaded before the operating system starts, and thus make it effectively impossible for the operating system to detect their presence. This UEFI secure boot process is an attempt to prevent that kind of rootkit from working. They describe it right there in the page, look at the Figure 2 diagram for current boot processes and the Figure 3 diagram for what UEFI secure boot does.

      Google's Chromebook devices use the exact same feature, for the same reason. A rootkit that hijacks the boot process can run undetected in Linux, Solaris, Mac OS X, or FreeBSD just as well as it can in Windows, we're just fortunate that current rootkits mostly target Windows because there are more potential victims out there.

      Admittedly Microsoft is not shy about working in its own best interests. I fully expect that some significant portion of the machines that ship with UEFI configured to make it effectively impossible to install any operating system other than the Microsoft operating system it received from the original equipment manufacturer. But the technology itself is not primarily aimed at blocking adoption of Linux, it's a true security feature. The next time you purchase a PC or motherboard, just make sure it can boot additional operating systems before you buy.

    27. Re:Translation by LWATCDR · · Score: 3, Insightful

      The OEMs for the most part will make it a user option for a simple reason.
      A lot of people when Windows 8 comes out will want to keep Windows 7. If they have an install disk and it doesn't work their will be hell to pay.
      Right now the UEFI folks are all going to be putting in an option to turn it off. Intel will without a doubt have that option in all of their reference motherboards which is what a lot of the OEMs use.
      ASUS will put in that option as well.

      The problem will be when at some point in the future someone has an old crappy Ultra book made by Ikkkiianu and wants to put Linux on it because Windows 9 doesn't work well on it and Windows 8 is too insecure.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    28. Re:translation by GameboyRMH · · Score: 1

      Yeah buncha Chicken Littles. After all their talk of doom and gloom about locked-down mobile devices, you can still buy open phones and tablets today. Not like their crazy cyberpunk dystopia where only a few devices could even be hacked to allow an open OS to be installed.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    29. Re:Translation by JamesP · · Score: 1

      Exactly

      This is a mixture of corporate greed and engineering mentality of NIH syndrome

      And of course, vendors took ages to implement UEFI, MS took ages to boot from UEFI, etc, etc

      --
      how long until /. fixes commenting on Chrome?
    30. Re:Translation by MrHanky · · Score: 4, Insightful

      I'm well aware of how to buy computers, thank you very much. I'm just pointing out that forcing people to pay for Windows isn't new, and has fuck all to do with control. betterunixthanunix's "translation" is just a bunch of hyperbolic nonsense based on the theory that Microsoft will always be more evil than Satan himself, despite whatever the people at Microsoft claim themselves.

      Of course, since this is Slashdot, facts are flamebait and paranoid fantasies are insightful.

    31. Re:Translation by Hatta · · Score: 3, Insightful

      But only some. Today you can throw Linux on any old hardware, and do something useful with it. 5-10 years from now, you'll have to specifically hunt down unlocked hardware. This has a rather drastic effect on the utility of Linux, which is Microsoft's intention.

      --
      Give me Classic Slashdot or give me death!
    32. Re:Translation by HJED · · Score: 2

      They appear to be adding SSL style authentication of boot loaders, however many OEMs will distribute with only the equivalent of a root certificate for Windows meaning they would not boot linux (or any other OS) without disabling this feature .
      The article is saying that to sell Win 8 logo branded products manufactures will have to support this feature, but there will be an option for OEMs to add more certificates and a setting to turn it off.

      --
      null
    33. Re:Translation by Hatta · · Score: 1, Insightful

      The technology is clearly intended to block adoption of Linux (and other operating systems), or they'd provide a way for the owner of a device to whitelist new operating systems. BIOS rootkits are a convenient excuse.

      --
      Give me Classic Slashdot or give me death!
    34. Re:translation by DaMattster · · Score: 1

      "Microsoft will attempt to use our gorilla status to force OEMs to lock out non-Windows operating systems, but ultimately, it's their decision as to whether they want to make it possible for you to run what you want on their computer, or whether they want us to not bomb them into the stone age and build a parking lot on the smoking ruins of their company."

      The open source community is no longer a fringe and it grows as the years go by. If the OEMs want to engage in this behavior, members of the open source community (and I include myself as I run OpenBSD) could always just do an end run around the problem. In fact, with coreboot, the open source BIOS, it already makes easier. Also, there is nothing stopping us from building our own PCs and just voting with our wallets.

    35. Re:translation by GameboyRMH · · Score: 1

      Best translation yet.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    36. Re:Translation by redbeard55 · · Score: 1

      Problem is the majority of users won't demand this . . . How many non geeks even know what linux is? I see it as a potential problem for at least a few years until the OEMs get tired of the geeks complaining about it.

    37. Re:translation by hairyfeet · · Score: 1

      Not to mention Win 8 is gonna be a WinME sized Vistabomb so any OEM that doesn't make it trivial to put Windows 7 on it will be committing suicide. I mean have you SEEN the Metro UI? Its a fricking cell phone OS! I have shown the screencaps to over 100 of my customers, a good sampling of everything from artists and engineers to carpenters and housewives and NOT A SINGLE ONE has had anything positive to say or would like to run it. The closest I got was this conversation: "That is a nice looking cell phone, is it Android? I've heard of that, its supposed to be good....what do you mean its Windows? windows what? THAT is the new Windows? that's just stupid! Its a cell phone! why would I want my computer to act like a cell phone?"

      Mark my words, Win 8 is gonna clear the room faster than a gassy fat guy after a chili cook off, guys like me will spend a good year or more being paid to rip the damned thing out like we did with Vista, and the ONLY nice thing is Ballmer may FINALLY be forced to "pursue other interests" and then hopefully they can get a CEO with a clue, maybe Ozzie or one of the Office team to right the ship.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    38. Re:Translation by houstonbofh · · Score: 3, Insightful

      No, just representative of the techs who support and choose company PCs. I got to change the corporate laptop standard from HP to Asus for problems like this. And the suits liked the new laptops.

    39. Re:Translation by houstonbofh · · Score: 1

      Most people choose there own mobile phone. Most people do not choose the company PC. It is often the technical people who choose that. (There are exceptions, but I usual do not work there long... Supporting 18 different desktops and 30 different printers is no fun)

    40. Re:Translation by Bing+Tsher+E · · Score: 1

      The hardware vendors are also vigorously trying to make certain there isn't any 'old hardware' to employ. The local thrift stores here have a deal with Dell where any old computer hardware that gets donated is whisked off to a shredder/recycler and they are compensated by Dell. It is marketed as a 'green' thing but it's quite the opposite of reuse-recycling. A lot of curious young people have gotten involved in tech because of a surplus of cool old gear being out there to fool with. A lot of people explore things like Linux by throwing it on the old box in the corner first to try.

      It won't matter whether the old hardware can boot Linux if it's been sucked out of existence and destroyed.

    41. Re:Translation by peragrin · · Score: 0

      Apple wasnt given a choice it was either EFI or BIOS for the switch to intel chips however Apple doesnt lock out other OS's on their systems yet still has restrictions for their OS.( Apple OEM install discs only install on hardware they came with, within the model. Mac mini install discs wont install on a macpro. Macbook discs dont install on an imac. Or you can buy the full version which installs on everything mac.

      Restricted yet easy far more open than MSFTS stupid plan.

      --
      i thought once I was found, but it was only a dream.
    42. Re:Translation by houstonbofh · · Score: 1

      You have a very odd definition of 'working OK'.

      See IBM, Dell, HP.

      Counter with Intel, Asus, and Acer. The Intel reference boards are very open (and some even overclock), and Asus and Acer are as well.

    43. Re:Translation by scamper_22 · · Score: 1, Insightful

      And good on MS.
      They're doing the work, they want to make sure they get paid.

      Maybe one day you will realize that every field protects itself. Doctors and lawyers restrict their trade. Regulators and government employees have direct access to government cash.

      What do tech companies have? They have their own community fighting to destroy any sense of long term cash flow.

      It was easier back in the day when this cash-flow came from a telecom monopoly which was then funded to R&D labs. But with the breakup of the telcos and vendors forced to fight on their own, they have to deal with the realities of funding a long term business.

      You want nice open standards... then do it but then have a license fee or tax that goes back to the creators of said standard.

      I have a feeling as the economy implodes... more and more people are going to realize that making a living is a pretty important part of life.

    44. Re:Translation by Anonymous Coward · · Score: 3, Insightful

      ACPI was not designed by Intel alone, Microsoft was also there. And let's remember what Microsoft tried to do [slated.org]:

      Translation: "We're doing all the work, how do we prevent the freeloaders from benefitting ?"

      Ah, the battlecry of the American People(see healthcare, welfare, etc).

    45. Re:Translation by betterunixthanunix · · Score: 4, Insightful

      As if I have never heard of a rootkit?

      In all seriousness, here is another method of solving the problem, which would be just as effective at preventing rootkits from hiding in the bootloader: make the boot medium a flash device on the motherboard, and have a jumper that enables writes to that device. This would not rob users of control over their system (although it may force people to get over their fear of opening their computer's case and changing a jumper), and would be just as effective at stopping the overwhelming majority of rootkits.

      The real motive here is the same as it ever was with the TPM: they want to market Windows as a "media platform" and their "media partners" do not like the idea of users being able to control their own computers -- they want to enforce restriction technologies. GNU/Linux is an operating system that its users control, and so these "media partners" do not want to see it installed on anyone's computer. Likewise, they do not want to see people modifying Windows in a way that circumvents DRM. They want computers to be like cell phones and cable TV boxes, herding the users in ways that are convenient for various copyright-based corporations.

      That this will block certain classes of rootkits is entirely incidental, despite the heavy marketing.

      --
      Palm trees and 8
    46. Re:translation by houstonbofh · · Score: 1

      I would say that only Microsoft could be that dumb, but they are only following the trail blazed bu Ubuntu and Gnome. I agree that the first batch of locked down systems that can't run Win7 or Linux will be very hard to move. The second batch will be wide open!

    47. Re:Translation by nschubach · · Score: 2

      In all seriousness, here is another method of solving the problem, which would be just as effective at preventing rootkits from hiding in the bootloader: make the boot medium a flash device on the motherboard, and have a jumper that enables writes to that device.

      Heck, a $0.10 switch on the back of the case...

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    48. Re:Translation by Anthony+Mouse · · Score: 5, Insightful

      Maybe one day you will realize that every field protects itself. Doctors and lawyers restrict their trade. Regulators and government employees have direct access to government cash.

      Economists call this behavior "rent seeking" and it is considered inefficient and undesirable. The idea that Microsoft should not be criticized for engaging in it is highly misguided.

    49. Re:Translation by Nerdfest · · Score: 2

      Did you notice the latest HTC policy change on locked bootloaders? There was a huge outcry, and the company did respond.

    50. Re:Translation by Anthony+Mouse · · Score: 1

      The problem will be when at some point in the future someone has an old crappy Ultra book made by Ikkkiianu and wants to put Linux on it because Windows 9 doesn't work well on it and Windows 8 is too insecure.

      That is one of the problems. The other problem is that by the time Windows 10 comes around and nobody has any interest in running Windows 7 or any other version that lacks support for this feature, the incentive for OEMs not to make it mandatory becomes much reduced.

    51. Re:translation by Nick+Ives · · Score: 1

      I despair, how is this insightful? MS isn't going to bully OEMs into doing anything. They've already been dragged through the courts for bullying OEMs during their anti-trust days, I'm sure they realise it's not worth it.

      What will happen is that some OEMs won't release certificates allowing you to install third party OSs. Most major OEMs like Dell, HP and Lenovo will allow it.

      This won't affect most home users who care about these things as we all build from scratch, no? Except for laptops of course, but I'd be amazed if the big OEMs shot themselves in the foot by making it hard to install your own OS. In fact OEMs have to sell you PCs with no OS installed if you ask as the competition authorities have taken the view that insisting that a machine should come with Windows is unlawful tying.

      --
      Nick
    52. Re:translation by SuricouRaven · · Score: 1

      The open source community is still a pathetic joke in the desktop world. Servers, yes, open source matters - linux is installed on more servers than Windows. But the desktop? Influence, negligable. And it's going to stay that way, no matter how good linux gets, because Microsoft has the advantage of dominance - they make the OS every hardware manufacturer writes and tests drivers for, every popular PC game is written to run on, and that just about every piece of software will run on. Just being on top gives them the advantage that lets them stay on top.

    53. Re:Translation by Anonymous Coward · · Score: 0

      Even if all "other" OS's came to 5% market share, this is below the 20% threshold any OEM would bother with. Sure, you'll have a few companies that will sell the product to the niche, but at exaggerated prices (see Linux laptops and desktops (ones that do not come with Windows at all) - yes, the crapware installed can reduce the cost of the PC, but if 20 pieces are installed, at $2 per piece, that would still not offset the differences I have seen).

      So, your typical CEO will say, humm, 95% market share with 0 extra cost so can sell at $X, or add in and test feature Y(Linux UEFI) at $0.02 per computer and sell to 95% of market at X+0.02.... guess what's going to win? Irregardless of the market forces for the 5% asking for something different!

      I believe this is why TV, Video Games, and Media (Music/Art) has been going downhill for quite some time now; the media companies don't want to risk "money" on the 20%, so will only cater to the 80%, leaving anyone that wants something "different" out! Join the masses or suffer/pay seems to be the mantra in the consumer world, and now it's finally caught up to the technological world.

      All I can say is thank-you to Indie games and media or I'd find life very boring :)

    54. Re:Translation by Anthony+Mouse · · Score: 1

      The sad thing is that basically anything can execute arbitrary code. You can't just sign the boot loader, you then have to have a boot loader which checks signatures on the kernel, a kernel which checks signatures on the drivers, etc. Then all it takes is for one obscure hardware manufacturer to get a driver signed with a buffer overflow in it, or for enough hardware manufacturers to not sign their drivers so that all the users allow unsigned drivers, and the malware authors are back in business -- but without helping Linux any, because you can't exactly load 2/3rds of Windows to get to the point where you can run arbitrary code in Ring 0 and load the Linux kernel.

    55. Re:Translation by spire3661 · · Score: 2

      The problem is they were allowed to take this mentality way too far. Once you are a convicted abusive monopoly, all your standard asshole tactics become super magnified.

      --
      Good-bye
    56. Re:translation by HeckRuler · · Score: 1

      "...and since it is ENTIRELY THEIR DECISION not ours, we're not liable for anything. Suck it."

    57. Re:Translation by spire3661 · · Score: 1

      Got a link? I did some cursory googling but i got nothing.

      --
      Good-bye
    58. Re:Translation by Anthony+Mouse · · Score: 1

      In all seriousness, here is another method of solving the problem, which would be just as effective at preventing rootkits from hiding in the bootloader: make the boot medium a flash device on the motherboard, and have a jumper that enables writes to that device. This would not rob users of control over their system (although it may force people to get over their fear of opening their computer's case and changing a jumper), and would be just as effective at stopping the overwhelming majority of rootkits.

      You don't even need a jumper or a flash device. All you have to do is to forget about digital signatures and use one-time authorization in the BIOS or EFI menu: If you install a boot loader the firmware has never seen before, when you try to boot it you get a message that says "boot loader is not authorized, if you have not just installed a new operating system this could be a rootkit etc., click here to use your previous boot loader instead," and all you have to do is go into the menu if you want to authorize the new one. But since there is no way for the rootkit to do that by itself, since the menu has its own read-only keyboard drivers and requires input from the keyboard, the only way you get a rootkit is if you go into the menu by hand and authorize it.

    59. Re:Translation by Anonymous Coward · · Score: 0

      Really, Intel and AMD should join forces in this: Make 'to change monitor brightness write a value from 0 (darker) to 0xff (brighter) to register 0xABC PERIOD'. "but but but", "I SAID PERIOD".

      Good idea, let's implement that using SOAP!

    60. Re:Translation by Anonymous Coward · · Score: 0

      Really, Intel and AMD should join forces in this: Make 'to change monitor brightness write a value from 0 (darker) to 0xff (brighter) to register 0xABC PERIOD'. "but but but", "I SAID PERIOD".

      Ten seconds later...

      "And in business news today, software giant Microsoft has issued a press release stating their intent to buy Intel. When questioned about possible anti-trust implications, Microsoft CEO Steve Ballmer was quoted as saying 'We own enough fucking senators to make this happen, asshole. If you've got a problem with it, we probably own a senator near you somewhere, and we'll just get him to fucking kill you. We've done it before and we'll do it again'. When it was pointed out that the interviewer lived in Canada and was thus outside the jurisdiction of the United States Senate, Mr. Ballmer stared back at him, his face almost glowing red with rage, turned around to a nearby Redmond police officer, babbling incoherently with anger, took his gun, and shot our man in the field. He will be missed. The Redmond police force in attendance applauded the action politely and nervously as Mr. Ballmer proceeded to do a dance that our cameraman, now safely thousands of miles away, charitably describes as 'embarrassing'. Next up, on the lighter side..."

    61. Re:translation by 0123456 · · Score: 1

      Most major OEMs like Dell, HP and Lenovo will allow it.

      What's the point of signed boot-loaders if the OEMs release keys allowing anyone to sign their rootkit?

      This 'security' only works if it prevents anyone other than 'trusted developers' (i.e. Microsoft) from releasing signed code.

    62. Re:Translation by scarboni888 · · Score: 1

      Sounds like a lotta fear-based drivel to me. The needs of the many far outweigh the needs of the few, son.

    63. Re:Translation by DavidTC · · Score: 1

      I don't know why people are assuming that previous MS OSes won't be, or even aren't already, signed.

      --
      If corporations are people, aren't stockholders guilty of slavery?
    64. Re:Translation by JamesP · · Score: 1

      Well, they could have gone with Openfirmware

      Of course, there would be some time adapting it to x86, etc

      Still, EFI is a way better option than BIOS

      --
      how long until /. fixes commenting on Chrome?
    65. Re:Translation by NJRoadfan · · Score: 1

      Reality is most thrift stores aren't taking in old tech, period. Many are turning away perfectly good TVs because they have dial tuners and are "too old", never mind the fact that practically all TVs prior to 2006 require a DTV converter. Its annoying to me because it cut off a source of equipment to keep my vintage machines (both computers and consumer electronics) running. Take a look on ebay at the prices of 486s. Used to be you couldn't give them away for free, now they actually fetch some cash because they have become hard to find. (mostly due to recycling and thrift stores not wanting to carry them)

    66. Re:Translation by chronoglass · · Score: 0

      they're just going to charge an extra 20 for an "app" to unlock the boot loader..
      honestly.. with the way that most idiots use a computer, I'm glad someone is locking the things down "or at least trying"

      if you want it.. it will be figured out.
      if you don't.. hey, ios doesn't have any viruses/malware unless it's rooted (aka controlled by the user)

    67. Re:Translation by gtall · · Score: 1

      "the only way you get a rootkit is if you go into the menu by hand and authorize it"

      And Mr. Clueless CEO will do just that to see the bouncing bunnies.

      Anyhow, all these "stand on your head and hop up and down" scenarios for using a non-MS OS are precisely what MS wants.

    68. Re:Translation by jedidiah · · Score: 1

      > Maybe one day you will realize that every field protects itself.

      Your Ayn Rand screed is unconvincing and is degrading the nature of business interactions to the point that anymore you need Perry Mason to bludgeon the other guy just so he honors the contract he signed. Never mind about any other more liberal notions about social justice and whatnot.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    69. Re:Translation by jedidiah · · Score: 2, Insightful

      You're an idiot to base any argument on what Microsoft SAYS they will do.

      They only thing that is remotely relevant is what they have actually done.

      Do they have that well established history of not being totally evil yet? Can you point to it as a counterexample to everyone else's paranoid?

      If not then you really have nothing to add to this conversation.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    70. Re:Translation by jedidiah · · Score: 2

      Yeah but Microsoft is head cheerleader for Team DRM. This is a big part of the problem.

      If the AACS cartel tells Gates to get on all fours and bark, he'll do it. Microsoft has gone there and done that already. They just might dictate draconian UEFI lockdown to keep special DRM stuff that they've already got and no one else does (BluRay, CableCard).

      --
      A Pirate and a Puritan look the same on a balance sheet.
    71. Re:Translation by snowgirl · · Score: 0

      Really, Intel and AMD should join forces in this: Make 'to change monitor brightness write a value from 0 (darker) to 0xff (brighter) to register 0xABC PERIOD'. "but but but", "I SAID PERIOD".

      According to my standards guides, the term is "full stop" not "period". (*/sarcasm*)

      --
      WARNING! This girl exceeds the MAXIMUM SAFE standards established by the FDA for BRATTINESS
    72. Re:Translation by Anonymous Coward · · Score: 0

      Except that microsoft has always been more evil than satan himself and continues to be so. i dont see any change in this policy (do YOU see a bios screenshot where you can load your own keys from usb sticks ? no ? then why do you think micro$hit has changed direction ?)

    73. Re:Translation by Curunir_wolf · · Score: 1

      Economists call this behavior "rent seeking" and it is considered inefficient and undesirable. The idea that Microsoft should not be criticized for engaging in it is highly misguided.

      File this under "unclear on the concept". Rent seeking has nothing to do with expecting compensation for producing value, or improving efficiency, or spending years (and vast sums of money) on education and certification in a field. Rent seeking attempts to close markets to competitors without actually producing anything.

      I checked Wikipedia and there's a pretty good definition there:

      The simplest definition of rent-seeking is the expenditure of resources attempting to enrich oneself by increasing one's share of a fixed amount of wealth rather than trying to create wealth. Since resources are expended but no new wealth is created, the net effect of rent-seeking is to reduce the sum of social wealth.

      That doesn't really describe the situation that the OP was describing: "It seems unfortunate if we do this work and get our partners to do the work and the result is that Linux works great without having to do the work."

      Gates felt that Linux devs gained some sort of undue enrichment. It's a bogus and douchbag position, but it's not "rent seeking".

      --
      "Somebody has to do something. It's just incredibly pathetic it has to be us."
      --- Jerry Garcia
    74. Re:Translation by Curunir_wolf · · Score: 2

      Sounds like a lotta fear-based drivel to me. The needs of the many far outweigh the needs of the few, son.

      Thanks, Karl.

      --
      "Somebody has to do something. It's just incredibly pathetic it has to be us."
      --- Jerry Garcia
    75. Re:Translation by murdocj · · Score: 1

      Right. Because 2012 is the year of Linux on the desktop.

    76. Re:Translation by Anonymous Coward · · Score: 0

      More "We won't screw you over, we have people to do that for us".

    77. Re:Translation by aaron552 · · Score: 1

      I don't know why people are assuming that previous MS OSes won't be, or even aren't already, signed.

      ...or that the windows 8 boot loader can't boot windows 7 perfectly well

      --
      I had a sig once. It was lost in the great storm of '09.
    78. Re:Translation by erroneus · · Score: 4, Insightful

      ...you mean the same way Microsoft benefited from the work of IBM and other software vendors? Gates and Microsoft understand the ecosystem which requires sharing. They were and still are interested in embracing that ecosystem and then locking everyone into their twist on what they take from it. This can be seen everywhere and in everything they do. The Java law suit against Microsoft is probably the best example of this behavior by Microsoft but there are hundreds of other great examples out there.

      Saying "we did the work..." is bullshit. They give away LOTS of things and waste LOTS of money. Their little bit associated with ACPI is a speck of dust in a drop in the barrel. This isn't about their trying to keep their work to themselves, it's about keeping the rest of the world from being compatible.

    79. Re:Translation by Anonymous Coward · · Score: 0

      Ooh, 18 desktops. You really think that's a lot???

    80. Re:Translation by Anthony+Mouse · · Score: 1, Insightful

      Gates felt that Linux devs gained some sort of undue enrichment. It's a bogus and douchbag position, but it's not "rent seeking".

      You're reading his bogus defense of his conduct and ignoring the conduct. Copyright and patent holders do this on a regular basis. They say that they created something and demand remuneration, but what they demand is far in excess of what they contributed. The patent holder patents the parts to his copy machine, but then tries to leverage the "legitimate" patent monopoly over replacement parts into a monopoly over copier service. The motion picture industry takes their oligopoly position in copyrighted motion pictures and tries to leverage it into control over the distribution channels, and then over all consumer electronics.

      If Microsoft breaks ACPI for Linux, they break more than they built. They are (to use the Microsoft camp's philosophy and terminology) "stealing" the benefit to the hardware makers who developed ACPI of selling ACPI-functional hardware to users of non-Microsoft operating systems. They are also ignoring the legitimate work done by the Linux camp to make ACPI work on Linux, as though somehow only Microsoft's efforts to make ACPI work for Windows are legitimate and require compensation and consideration but any efforts by a third party to make it work for another operating system can be ignored in the calculations.

    81. Re:Translation by Anthony+Mouse · · Score: 1

      1) Corporations would naturally have a BIOS password which only the IT department would know, and they would know better than to type it just because the dancing bunnies "for some reason" require you to install a boot loader.

      2) If you can convince the user to reboot the computer, enter the BIOS and change the authorized boot loader by hand in order to see some lolcats, there is just nothing you can do to overcome that level of stupidity. You might as well worry about a denial of service attack whereby the website instructs the user to stick a fork in the electrical outlet. If the user is that stupid, you lose, and you deserve to lose.

    82. Re:Translation by Bengie · · Score: 2

      A read-only bootloader is a horrible idea for a common desktop computer. IT would hate you.

      "That this will block certain classes of rootkits is entirely incidental"

      If everything from the boot process to the software is signed and requires signature, malware's only hope to getting installed is bugs in the OS, and even then, it would go away on reboot. Even if the malware could insert itself into some start-up location, it would never start because it wasn't signed. The uEFI won't load it, the bootloader won't load it, the OS won't load it.

      I fail to see how this is bad.

    83. Re:Translation by nabsltd · · Score: 1

      Heck, a $0.10 switch on the back of the case...

      With either option, add in logic so that the switch/jumper means "able to update bootloader" in one position and "able to boot" in the other. That way, you can't leave the switch in the position that allows you to have a rootkit install itself (unless you never reboot your computer...in which case a rootkit isn't really a problem).

    84. Re:Translation by SuricouRaven · · Score: 1

      No, you only need to get as far as the kernel. If you can be sure that is untampered-with, the antimalware programs can depend on it to return correct information they can use to spot malware.

    85. Re:Translation by betterunixthanunix · · Score: 0

      A read-only bootloader is a horrible idea for a common desktop computer. IT would hate you.

      Thus explaining why we are going to let OEMs decide whose bootloaders can be used?

      At some point the new UEFI boot process needs to allow IT departments to sign their own bootloaders. How is this different from allowing them to change a jumper to install a custom bootloader? Maybe I am just not familiar enough with how IT staff manage their boot media.

      I fail to see how this is bad.

      ...because it means that individual users will not be able to use a different operating system if the OEM decides not to allow it? Do you really want your laptop to use the same software restriction model that cell phones or video game consoles use?

      --
      Palm trees and 8
    86. Re:Translation by Anonymous Coward · · Score: 0

      Sent: Sunday, January 24, 1999
      yeah that is fully relevant 12 years later.

    87. Re:Translation by tripleevenfall · · Score: 1

      Ah, the battlecry of those who don't realize that giving someone a fish rather than teaching them to fish is not helping them.

    88. Re:Translation by MrHanky · · Score: 0

      If you were able to read, you'd see that I actually referred to what Microsoft have done in the past, compared it to what the OP claimed they and their OEMs would do in the future and found him to be full of shit. Microsoft's claims are circumstantial.

      But why am I even replying to this illiterate fool.

    89. Re:Translation by Rhywden · · Score: 1

      At some point the new UEFI boot process needs to allow IT departments to sign their own bootloaders. How is this different from allowing them to change a jumper to install a custom bootloader? Maybe I am just not familiar enough with how IT staff manage their boot media.

      Because IT staff now has to run around and flip a switch at every PC.

    90. Re:Translation by BJ_Covert_Action · · Score: 1, Funny

      ...betterunixthanunix's "translation" is just a bunch of hyperbolic nonsense based on the theory that Microsoft will always be more evil than Satan himself...

      Are you saying Microsoft isn't more evil than Satan himself? On Slashdot?

      Quick! Someone ready the stake and torches! We have a heretic to burn!

      P.S. Everyone watch where you step. He may have turned someone into a newt!

    91. Re:Translation by Smallpond · · Score: 1

      Yes, but when you turn off the security in order to boot another OS will you still be able to boot Windows? Doubt it.

    92. Re:Translation by Anthony+Mouse · · Score: 1

      Not really. Just because a signed kernel was loaded initially doesn't mean that's what is still running by the time the anti-malware program gets running. As soon as you have something malicious running with the ability to execute all privileged hardware instructions, there is no way to rely on anything anymore. The rootkit can just load a whole new kernel if it has to, or it can patch the running kernel in memory. The best anti-malware can do is to detect it before it executes in kernel mode and prevent it from executing. And trying to get the anti-malware running as early as possible only makes you more susceptible to rogue anti-malware.

    93. Re:translation by Anonymous Coward · · Score: 0

      Your analogy fails to make sense. Please explain what trail was blazed and how that related to Microsoft being dumb.

    94. Re:Translation by J'raxis · · Score: 1

      The moment Gates used the word patent, it became about rent-seeking. Patents -- paying the government for a monopoly privilege over an invention -- are a perfect example of the exact definition you posted.

    95. Re:Translation by Anonymous Coward · · Score: 0

      I wish more people would see that all intellectual property law is merely rent seeking behavior.

      Now, if you want to put in a contract that the purchase of your work cannot copy it, or do X with it and they do, that's a breach of contract. But if someone gets a copy of your work without agreeing to such a contract, they should be free to do with it what they please. This assumes of course that they did not steal actual property in order to get such a copy.

      I should also clarify, when I say "all intellectual property law", I do not necessarily include trademarks in that definition. I'm not familiar with but can assume the current trademark system is corrupt to one extent or another. However, the concept in and of itself is sound. If I develop a logo, a catchphrase, a brand of some sort and you use that brand, it is a form of fraud against the consumer. I don't believe any similar case can be made for copyright or patents.

    96. Re:translation by bws111 · · Score: 1

      Eh? The 'keys' you are referring to are a list of vendors you trust. Having said public key does not allow anyone to sign code. The whole point is that only developers you trust can sign code. If you trust Red Hat, you can run their signed code. If you trust Microsoft, you can run their signed code. Trusting Red Hat does not mean you can run Microsoft signed code, and vice-versa.

    97. Re:Translation by makomk · · Score: 2, Insightful

      Entirely coincidentally, most of the really buggy ACPI implementations out there - the ones that cause the most headaches for Linux and other OSes - are generated by a Microsoft tool that's carefully crafted to generate code that breaks under other OSes. It's probably also a coincidence that Microsoft encourages vendors to use WMI, a way of extending ACPI which means that every single laptop in existence needs its own drivers for stuff like hotkeys, backlight control etc, and these drivers are for some odd reason Windows only.

    98. Re:Translation by im_thatoneguy · · Score: 1

      Or Microsoft doesn't feel threatened by Linux on the desktop in the slightest and thinks it's prudent to stop the REAL problem for its customers: rootkits.

    99. Re:Translation by AvitarX · · Score: 1

      You mean like HTC committing to not do this?

      Samsung sending phones to Cyanogen in exchange for them promising support?

      From what I can tell it's working quite well in phones.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    100. Re:Translation by sgt+scrub · · Score: 1

      I read it as, "Consumers will be locked into Windows by the OEM's not us. No really. We have nothing to do with it. It is all up to them".

      --
      Having to work for a living is the root of all evil.
    101. Re:Translation by westlake · · Score: 1

      Today you can throw Linux on any old hardware, and do something useful with it. 5-10 years from now, you'll have to specifically hunt down unlocked hardware. This has a rather drastic effect on the utility of Linux, which is Microsoft's intention.

      Thirty years of dirt cheap retrograde hardware has translated into a 1% share for Linux on the desktop.

      53% for the iOS in mobile.

      In theory you can throw Linux on any old hardware. But the OS and the applications it will run will have much the same flavor as an OSX or Windows PC of the same vintage.

    102. Re:translation by houstonbofh · · Score: 1
      From the parent post...

      I mean have you SEEN the Metro UI? Its a fricking cell phone OS! I have shown the screencaps to over 100 of my customers, a good sampling of everything from artists and engineers to carpenters and housewives and NOT A SINGLE ONE has had anything positive to say or would like to run it. The closest I got was this conversation: "That is a nice looking cell phone, is it Android? I've heard of that, its supposed to be good....what do you mean its Windows? windows what? THAT is the new Windows? that's just stupid! Its a cell phone! why would I want my computer to act like a cell phone?"

      Now look at Ubuntu Unity and the praise it has received... What? No praise? How about Gnome 3? What? Even Linus hates it?

    103. Re:Translation by houstonbofh · · Score: 1

      Ooh, 18 desktops. You really think that's a lot???

      With 150 users in three countries, and not knowing who is on what, yes. Note that I meant 18 different models, motherboards, vendors, drivers, CPUs... And which of the 5 different OEM CDs does this one need? Not 18 users.

    104. Re:Translation by WNight · · Score: 2

      Apple OEM install discs only install on hardware they came with [...]

      Gotta love it when a non-trivial amount of engineering goes into making the product less useful. What if your disc breaks and your friend doesn't have the same model?

      If they weren't total assholes the disc would work, but would bill the owner of that install serial number for another install unless they proved it was to replace broken media. But at best they'd still be inconveniencing you.

      Restricted yet easy far more open than MSFTS stupid plan.

      Meh. Not noticeably different really. Big stonewalling company, DRM, requiring permission to install, abusive EULAs, etc. When you haven't balked at giving them the ability to make you jump through hoops why begrudge them an extra hoop or two?

    105. Re:Translation by V!NCENT · · Score: 1

      No. Apple is using a BIOS with an EFI layer on top.

      So technically Apple took crap and put a tiny layer of extra crap on top.

      Ask yourself why we need formware that does nothing else but load a kernel? You need drivers for all your hardware anyways, so you might as well pass the still running firmware crap altogether...

      --
      Here be signatures
    106. Re:Translation by jbolden · · Score: 1

      That's only possible because Dell buys these things cheap. Old PCs get tossed in the garbage. They really are worth that little.

    107. Re:Translation by whit3 · · Score: 1

      Apple OEM install discs only install on hardware they came with [...]

      Gotta love it when a non-trivial amount of engineering goes into making the product less useful. What if your disc breaks and your friend doesn't have the same model?

      Well, it ain't pretty, but (1) you can restore from a bootable
      backup disk, or (2) you can SOMETIMES get a disk
      replaced for shipping/handling (while stocks last, for
      new machines), or (3) an Apple dealer is authorized
      to reinstall your original operating system version (the
      license for that version is tied to the machine, by serial number).

      What USUALLY happens, though, is your friend
      boots from his install DVD, you hold down the "T" key and
      boot your machine into target disk mode, then your
      box is just an external drive for your friend's box, and the
      install proceeds as though friend was putting the OS onto his
      own disk. This requires a Firewire cable to link the two computers.

    108. Re:Translation by Anonymous Coward · · Score: 0

      In theory you can throw Linux on any old hardware. But the OS and the applications it will run will have much the same flavor as an OSX or Windows PC of the same vintage.

      True, however there is an important distinction... Linux is still being maintained.

    109. Re:Translation by jbolden · · Score: 1

      Lets be fair here. Linux failed on the desktop OTOH Linux has huge market share in many other areas and its ability to run on low end hardware helped in penetrate the departmental level server market.

    110. Re:Translation by jbolden · · Score: 1

      I believe this is why TV, Video Games, and Media (Music/Art) has been going downhill for quite some time now; the media companies don't want to risk "money" on the 20%, so will only cater to the 80%, leaving anyone that wants something "different" out!

      There is vastly more diversity in TV and Music than there was a generation ago. The problem, particularly in TV has been that customers are demanding diverse programming thus increasing production costs relative to viewership.

    111. Re:Translation by jbolden · · Score: 1

      Could be. Or it could be that the end user just needs to load a key for any kernel. A signed OS upgrade includes the keys for your hardware. An unsigned one requires the end user to know what they are doing. Fair for geeks, safe for non geeks.

      I agree that Paladium originally used the signed all the way down approach however.

    112. Re:Translation by jbolden · · Score: 1

      Microsoft already virtualizes most drivers. The "unsigned" drivers won't be executing at level 1, they will be running in level 3 user space. A buffer overflow won't matter, the virtual driver will just crash.

    113. Re:Translation by Anthony+Mouse · · Score: 1

      That isn't really much protection if you consider what drivers are. By their nature they have to have privileged access to hardware. So you don't have kernel mode yet, but you're a driver? You put some rootkit code in a noncritical register or buffer on whatever piece of hardware the driver is operating, then you instruct the device to write that data to a physical memory address where the kernel will eventually execute it in kernel mode.

      And that's ignoring the "most" -- if some drivers are not virtualized then all you have to do is have the click-happy user install the rootkit purveyor's own unsigned driver, which is one of the sort that has to run in kernel mode.

    114. Re:translation by hairyfeet · · Score: 1

      Bimbo Newton Crosby. this is even worse than the ribbon stupidity, because at least with that noobs like it, although there are a hell of a lot more experienced office users than noobs. You don't know how many told me variants on "oh thank God!" when i told them their old copy of Office 2K or 2K3 would run on Windows 7.

      To me the sad part if the Win 7 UI is probably the best damned UI MSFT has ever made. the search integrated into everything makes it simple for guys like my dad to find things while making it a hell of a lot faster than the old start>programs>drill down method for old hands. then taskbar jumplists and breadcrumbs just add to the speed. Even my old engineer customer, who has hung onto the Win2K UI all through XP has talked about how much quicker it is for him to get to the features he wants with Windows 7.

      Leave it to the sweaty monkey, the worst CEO since the sugar water guy, to cock up what is a truly brilliant design instead of building on what is already great. The win 7/8/9 legacy could be a dynasty like Win2K/XP was, but instead Ballmer is gonna royally screw the pooch, all because he has Apple envy so bad it hurts.

      I still think the Gates borg needs to be replaced by Ballmer with his tongue out wearing an "I Ape Apple!" beanie, as that is sadly the direction he is determined to go, customers be damned. Just look at Kin and Zune. the only nice thing I can say about win 8 is hopefully when it bombs Ballmer will be forced out, and they can bring back Ozzie or one of the Office Team to run things and turn this ship around. The only focus groups i can see liking Metro would be ones like that one customer who thinks it was a cell phone!

      --
      ACs don't waste your time replying, your posts are never seen by me.
    115. Re:Translation by HJED · · Score: 1

      I would assume you would, as otherwise win 8 would not be backwards compatible with older hardware.

      --
      null
    116. Re:Translation by WNight · · Score: 1

      Does that leave you with the wrong OS version for that hardware?

    117. Re:Translation by jbolden · · Score: 1

      That's not the way drivers work in modern windows. The way windows works is there is a generic driver written by microsoft that runs as the driver and then there is essentially a user application and datafile which is the hardware specific driver. The hardware never interfaces directly with the virtual drivers.

      So what will happen is:

      a) There are Microsoft drivers
      b) There are user mode virtual drivers
      c) There are signed drivers

      What won't exist are unsigned non-user mode drivers.

    118. Re:Translation by Waccoon · · Score: 1

      Make 'to change monitor brightness write a value from 0 (darker) to 0xff (brighter) to register 0xABC PERIOD'.

      Does this really need to be done in software? I'm getting really annoyed that all my buttons are disappearing.

      256 values for brightness definitely isn't enough. When will HDR finally become standard? 2030?

      Meanwhile, finding a good monitor NOT based on a TN panel is difficult. What ever happened to E-IPS? Screw extra software to get rid of perfectly functional buttons. Give me hardware that isn't crap.

    119. Re:Translation by PoopMonkey · · Score: 1

      That's what apple is known for. They're one of the few companies that has actually managed to polish a turd.

    120. Re:Translation by madhi19 · · Score: 1

      And what do you do five years from now when all motherboards are locked on Windows 8. And they conveniently forgot to release the key or give you the option of turning that shit off. What Microsoft want you to believe is that it will only be the OEM making that change but the motherboard makers are taking their lead from OEM. If only Dell had the guts to tell Microsoft where they can shove their stickers! Anyway it the first thing most peoples remove five minutes after unboxing the hardware.

    121. Re:Translation by madhi19 · · Score: 1

      Yeah but you never know Microsoft might be afraid that 2012 is the year that Apple will say. "Let screw Microsoft and release OSX for every hardware!" Or 2012 might be the year when Google say. "Android 5.1 Desktop Edition how about it?"

    122. Re:Translation by davester666 · · Score: 1

      Only if your friend has just bought the latest Mac, released AFTER Apple has last revved OSX [in general, there have been maybe a handful of times when they've had model-specific updates to OSX].

      Using the DVD for his Mac, he installes the model-specific version of OSX for his Mac on your computer's drive [which is fine in this case, say 10.7.0]. Then reboot, again with your computer in target disk mode, but now his computer boots from your internal drive. Update to the lastest version, say 10.7.1 which is not model specific. Now you have a regular version of OSX on your drive, same as if you had installed it using the 'correct' DVD for your model and then updated it.

      --
      Sleep your way to a whiter smile...date a dentist!
    123. Re:Translation by JamesP · · Score: 1

      Yes, having the HW buttons is nice, but it needs to be done in SW as well for power saving purposes (and be configurable in the OS)

      Still, for the most part, the buttons usually trigger the OS to change the brightness

      --
      how long until /. fixes commenting on Chrome?
    124. Re:Translation by WNight · · Score: 1

      Thanks, that could be helpful.

    125. Re:Translation by JamesP · · Score: 1

      As far as I know, all EFI implementations are like that

      It's not really 'EFI on top of Bios' but they kept the menus the same, etc

      --
      how long until /. fixes commenting on Chrome?
    126. Re:Translation by whit3 · · Score: 1

      [about a machine-specific install DVD and
      install using the intended machine onto
      an unintended target's disk]

      There's no guarantee, of course, that the
      system as installed is suitable (the target
      machine could be one of the old 68k Mac
      models, if it had a big enough drive). You
      can test easily enough, by holding down T
      while booting the friend's Mac, then boot
      your target Mac with the 'option' key down,
      and choose to boot (if it's offered as an option) the
      'external disk' which is your friend's internal drive.
      You need to connect 'em with a firewire cable, of course.

      Buying a new system upgrade/install disk is a legal option,
      but none currently available from Apple work on
      (for instance) my trusty old G3 iMac. So, it's
      not always available.

    127. Re:Translation by Bengie · · Score: 1

      Where are you getting this info that IT can't sign their own boot loaders?

      "allow customers to import and manage those certificates, and manage secured boot"

      If the OEM doesn't allow it, don't buy it. In a market where competition is fierce and Linux is quite "main stream" for enthusiasts/servers, there will be someone else willing to allow certs to be managed.

  2. Useless response by Chrisq · · Score: 3, Insightful

    Summary:
    If the vendors don't provide a way to boot other systems its not our fault!

    1. Re:Useless response by Anonymous Coward · · Score: 1

      In unrelated news;
      Vendors which don't provide a way to boot other systems receive better pricing.

    2. Re:Useless response by GameboyRMH · · Score: 1

      Agreed, little more than shifting blame to the OEMs.

      They'll be free to maintain exclusivity agreements with MS which may require bootloader locking, or they can not sell any Windows PCs. If Klupendorf Computers in Switzerland is the last company on earth selling unlocked PCs at Alienware prices, well, tough luck, that's capitalism.

      I warned you fucking Apple fanboys this would happen. Thanks a lot, douchebags.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    3. Re:Useless response by HermMunster · · Score: 1

      Yes it it is anticompetitive behavior and a slight modification of embrace extend extinguish. Microsoft decides what security is. They determine if you are secure. They determine if they are secure. They deny you boot access with every turn in order to ensure vendors do not put competing OSes into consumers hands, and make it hard or seem insecure if you turn it off. For example the vendors turn it off to install other OSes, That puts their os at risk and probably denies win8 boot -- no secure boot then no win8 boot -- Microsoft cries foul.

      Microsoft can then claim only win8 is a viable and secure os. Governments will look at this for certification. Their server software will get chosen. Their people will get the contracts. Microsoft servers will gain share when now they are loosing it at a fast pace.

      This is clearly an anticompetitive process meant to shrink the base of competing products. If the small yet innovative distro like Mint can't afford this with every release. Thus they reduce their share -- they slow down the pace of their innovation by reducing the number of release cycles.

      Microsoft should not be in control of any certificate issuing program, and they should not set the criteria. They should go through the same process as anyone else. This way they can't use their monopoly power to deny competition a chance.

      And as far as I know, only Windows is currently at risk anyway from boot loader exploits. And Microsoft could more easily handle their boot exploit issues from within windows without endangering the viability of competing products. And this is clearly a major issue just because Microsoft is a convicted monopolist. Microsoft as a convicted monopolist should never be allowed to hold the keys to any program that can be used in improper ways and which they can use to kill or limit their competition.
       

      --
      You can lead a man with reason but you can't make him think.
    4. Re:Useless response by tixxit · · Score: 1

      It's a real shame too. Even if most higher end PCs add the "flexibility" to let linux boot no problem, I'd hate to be the kid that wants to experiment with his computer, but whose parent's didn't consider what BIOS came w/ it and whether it could boot Linux when they bought it. When I was a kid, my sound didn't work and my video card was barely supported, but at least I could boot and play around in Linux.

    5. Re:Useless response by Anonymous Coward · · Score: 0

      Why, exactly, are Apple fanboys to blame for this?

    6. Re:Useless response by GameboyRMH · · Score: 0

      Because you voted with your wallets for curated computing.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    7. Re:Useless response by SuricouRaven · · Score: 1

      Apple has been going down this route for a long time, leading the charge for strict manufacturer control of general-purpose hardware. There used to be a time when they were the champion of geeks, the only company capable of challenging Microsoft's dominance (And with a Unix deriv, even better!). But then they changed. They stopped being a computer company, and turned into more of a media and lifestyle company, and with that business model comes a need to exercise strict control. This is how we ended up with the iPad, a general-purpose computing device which is locked down tight to make sure it's incapable of doing anything that Apple hasn't explicitly deemed permissible.

      The Apple fanboys are to blame because they go on to buy the iPad and iPhone, seeing them only as shiny new hardware without admitting that the manufacturer-controls-everything model behind them is a threat to all technology enthusiasts. An effort to turn computers from something users can play with as they wish into a means of getting them new videos and games to pay for.

    8. Re:Useless response by StuartHankins · · Score: 0

      Go look up Palladium and see what that was/is all about. This wasn't Apple fans' fault. This is coming from your favorite company -- Microsoft -- who has been trying to stuff a dick into everyone's asses for decades. You're just mad because they told you it was a lollipop. But go ahead, blame everyone else for your lack of awareness. And for God's sake pull your pants up.

    9. Re:Useless response by Anonymous Coward · · Score: 0

      Better yet:

      If we tell the vendors that we (won't do bussiness with anyone who allows Linux/offer steep discounts to those who don't allow Linux), then it is their fault if the cave to our demands.

    10. Re:Useless response by jbolden · · Score: 1

      This is how we ended up with the iPad, a general-purpose computing device which is locked down tight to make sure it's incapable of doing anything that Apple hasn't explicitly deemed permissible.

      Will you stop. You buy a $99 developers license and you can create your own provisioning files for you and your friends and do whatever you want with an iPad. Apple is not exercising strict control. What they are doing is preventing end users from having to evaluate developers whom they don't know. And if you don't like Apple's policies, you can reset your authentication servers and have the iPad authenticate against different servers and Apple will sell you the complete software solution at below cost ($299).

      Yes, the system is secure by default. But that's it.

    11. Re:Useless response by jbolden · · Score: 1

      Then you run Linux on a VM and learn 95% of the same thing. And that's assuming you can't load something in windows to hack the bios and sign the Linux.

    12. Re:Useless response by Anonymous Coward · · Score: 0

      Correction:

      "If the PC vendors [that we have under our complete control] don't provide a way to boot other systems its not our fault!"

    13. Re:Useless response by SuricouRaven · · Score: 1

      So you can run anything you want, so long as you're willing to forgo access to the distribution system that is needed to get your software easily accessible to all, pay extra, and own a Mac. That hardly seems fair.

    14. Re:Useless response by jbolden · · Score: 1

      Yes you can run anything you want. Any anyone else who knows what they are doing can run anything they want. And if you want to distribute to the ignorant then and only then you need to get permission from the people protecting them. Seems very fair.

      Your claim was that you couldn't run what you want. This other weaker claim that Apple controls the default distribution mechanism, which is easily bypassable is true. The claim you cannot run what you want is not.

      As for needing to own a mac. In theory I imagine its possible to do this without a mac. The provisioning stuff is fully documented. Someone could write it all for Linux. In theory GNUStep might catch up enough with OSX's developer's environment to allow you not to own a Mac. They offer some weak control mechanism from PCs but they just migrated another whole class of their server class stuff down into OSX. OSX is the parent platform for iOS.

    15. Re:Useless response by Bengie · · Score: 1

      Fake News: In other news, OEM X hast lost millions of dollars because Linux runs over 50% of the internet and all those data centers can't use their servers. OEM Y saw this as an opportunity and now offers manageable certs.

      What makes you think OEMs won't allow manageable certs when it's easy for them to do so? Actually, it's beyond "easy" as the default is to allow it from UEFI motherboard makers. OEMs would have to specifically request to have that feature disabled. Also sounds like a great way for a class action law suit or even anti-trust.

      tin foil hat much?

    16. Re:Useless response by Anonymous Coward · · Score: 0

      In a sense they're right though. There are more than enough people out there who want to run Linux or BSD or even try to put OSX on their PC that some manufacturer somewhere will offer mobos or full machines with at least the ABILITY to turn secure boot off. Hell having the option in the EFI setup costs their users that want to keep secure boot enabled nothing, except they may have to put a password on the EFI setup, which if they're that security conscious, they should be doing anyway.

      Greater flexibility == lager customer base, so the only way I see companies removing this option from the firmware is if Microsoft makes that a condition of being a Microsoft OEM.

  3. Boo by Anonymous Coward · · Score: 0

    MS

  4. Hey Look! by Anonymous Coward · · Score: 0

    They aren't being as ruthless as we thought. How thoughtful of the evil geniuses.

  5. Just helps Apple... by Anonymous Coward · · Score: 1

    Microsoft killed the Hackintosh for Apple! How nice of them.

  6. translation by drinkypoo · · Score: 5, Insightful

    "Microsoft will attempt to use our gorilla status to force OEMs to lock out non-Windows operating systems, but ultimately, it's their decision as to whether they want to make it possible for you to run what you want on their computer, or whether they want us to not bomb them into the stone age and build a parking lot on the smoking ruins of their company."

    --
    "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  7. Empty promises? Hopefully not. by Anonymous Coward · · Score: 0

    Let's hope that this isn't an empty promise. Also, Microsoft should learn from the Sony disaster. Let the geeks use their Linux and they won't try to attack your servers.

    1. Re:Empty promises? Hopefully not. by Chrisq · · Score: 2

      Let's hope that this isn't an empty promise

      We're talking Microsoft here, you might as well hope that a leprechaun will bring you a pot of gold so that you can retire in never-never land and live happily ever after.

    2. Re:Empty promises? Hopefully not. by BJ_Covert_Action · · Score: 1

      You mean that's not going to happen?

      :*(

    3. Re:Empty promises? Hopefully not. by perryizgr8 · · Score: 1

      what sony disaster?? the one where ps3s are now the best selling consoles?
      lets face it, 99.999999% people don't care about booting anything. booting is just something between them and facebook, or modern warfare.

      --
      Wealth is the gift that keeps on giving.
    4. Re:Empty promises? Hopefully not. by westlake · · Score: 1

      Microsoft should learn from the Sony disaster. Let the geeks use their Linux and they won't try to attack your servers.

      Linux on the PlayStation is still dead.

      Attack the console servers and it is the console fans who be reaching for their pitchforks, the tar and feathers. There are more of them than there are of you.

      Tens of millions more of them than you.

  8. In other words by Nimey · · Score: 2

    if the computer's locked down, blame the OEM, not us.

    --
    Hail Eris, full of mischief...

    E pluribus sanguinem
    1. Re:In other words by ThosLives · · Score: 1

      I think the general problem is the concept that the organizations with the ability to lock (and unlock) the resources are not the end-users, but the manufacturers.

      It's the old tradeoff between responsibility and freedom: if computer users want "security" in their systems but don't want to be responsible for achieving that security (and instead give that responsibility to the hardware and software OEMs) then those users must by necessity give up some freedoms.

      I think the issue here is that moves like this don't even give users the option to make the choice - the freedom (and responsibility) has been taken from them without their consent. I suppose there may be an argument for removing some freedoms for "the greater good" (for example, if people have the option to have an unsecured machine and they get malware, that will affect many other people not just that individual) but that, in my opinion, is a philosophically dangerous argument.

      --
      "There are a dozen opinions on a matter until you know the truth. Then there is only one." - CS Lewis (paraprhase)
    2. Re:In other words by Anonymous Coward · · Score: 0

      Why not, it's worked out well for Google and Android phones. The OEMs load uninstallable bloatware, lock down the bootloaders, screw with the code, add their own UIs, and delay or outright decide not to support OS updates. All while Google turns a blind eye and washes its hands of it. And the Fandroid zealots, erm excuse me I mean the "totally unbiased average users", defend them at every turn from even the slightest implication that Google could take a bit more responsibility all while screaming that the system is still totally open (you just have to exploit this security hole to get access) and Google is the bestest ever.

    3. Re:In other words by maxume · · Score: 2

      What are you talking about?

      A motherboard or uefi vendor can a have a system giving the user the full ability to control the feature (a hardware switch, the ability to install new keys, etc), or they can only install Microsoft's keys and lock the user out. So it really matters what the actual practice ends up being, and it isn't at all clear what is going to happen.

      It doesn't seem that likely to me that the various hardware vendors will shoot themselves in the feet by locking to Microsoft here (Microsoft won't bother with incentives, they are smart enough to know that won't fly with regulators).

      --
      Nerd rage is the funniest rage.
    4. Re:In other words by bluefoxlucid · · Score: 2

      This is why I ran from Motorola's bull shit and moved to Samsung. Yes, Samsung phones eventually EOL; but they're decent anyway, whereas Motorola is trash that you wait for updates to more trash. An outdated Samsung Dart is a decent phone, even though it's slow and lacks RAM and has some funny version of Android (2.2) and won't get 3.1 any time soon.....

    5. Re:In other words by Dishevel · · Score: 0

      I love my HTC Evo.
      Rooting was simple.

      I would definitely make my next phone the Sprint Nexus S.
      Google keeps their phones unlocked.
      Would you like Google to launch missiles at phone makers and vendors till "They do what Google wants"?

      I for one believe there will be a hardware switch to allow signing of a new OS.
      For most Microsoft users opening the case is a non starter any way. This will allow the stupid to have secure computers and the rest of us can do as we please.

      --
      Why is it so hard to only have politicians for a few years, then have them go away?
    6. Re:In other words by houstonbofh · · Score: 1

      Funny... The vendor with the biggest slice of the Android market (HTC) has mostly unlocked phones... If this translates to the PC field, Dell will be open, and HP/Compaq will still suck. I am OK with that.

    7. Re:In other words by Anonymous Coward · · Score: 0

      I love my HTC Evo.
      Rooting was simple.

      I'm glad you're okay with the fact that the device is easy to exploit. In other OSes, we used to call these kinds of things "security holes".

      I would definitely make my next phone the Sprint Nexus S.
      Google keeps their phones unlocked.

      I'm glad Google does this. It does show though that they are perfectly capable of exerting at least some influence over the carriers and OEMs. It'd be nice if they did this for more than just one phone on a few carriers.

      Would you like Google to launch missiles at phone makers and vendors till "They do what Google wants"?

      No but it would be nice if they stopped pretending that their end-product is "open" if they're going to allow the manufacturers to lock it down. Google isn't helpless here, they control the license.

      I for one believe there will be a hardware switch to allow signing of a new OS.
      For most Microsoft users opening the case is a non starter any way. This will allow the stupid to have secure computers and the rest of us can do as we please.

      It's quite telling that you view those that would want to use this secure boot feature as "stupid". I'm willing to bet you're not as technically inclined as you think you are. Generally the people that label users as "stupid" are in fact bad developers or bad IT people themselves that have an over-inflated opinion of themselves.

    8. Re:In other words by Anonymous Coward · · Score: 0

      Funny... The vendor with the biggest slice of the Android market (HTC) has mostly unlocked phones... If this translates to the PC field, Dell will be open, and HP/Compaq will still suck. I am OK with that.

      Unlocked != open

      Take a HTC phone running Android.

      Can you uninstall the bloatware without rooting?
      Can you install OS updates as soon as Google comes out with them without rooting?
      Can you load a new ROM without having to root or go around the bootloader?

      If you answered 'no' to any of these questions then congratulations, your HTC phone is not open. The fact that it is unlocked has nothing to do with it.

    9. Re:In other words by Anonymous Coward · · Score: 0

      It's quite telling that you view those that would want to use this secure boot feature as "stupid". I'm willing to bet you're not as technically inclined as you think you are. Generally the people that label users as "stupid" are in fact bad developers or bad IT people themselves that have an over-inflated opinion of themselves.

      Those of us with the ability to open a case will hit the switch, approve the new OS, then switch back to secure.
      Microsoft Windows is a shit OS. Always has been. Only reason I ever boot into it is at work to run a radio programing app that I have as yet been unable to get running under Linux. I also have 2 Windows servers for some proprietary software and 2 Windows XP Pro machines running stuff that only runs in Windows.

      I would definitely use the secure boot. I would not run the system the whole time with the hardware switch turned off. The switch should be used to self sign a boot loader or OS. Once that is done you go back into secure mode. I do not see how my meaning was unclear in any way. Perhaps you have much love for Windows and just needed to attack me. A little reading of the things that you are quoting might go a long way in understanding.

    10. Re:In other words by TheSpoom · · Score: 2

      Please also ignore the fact that our contract with the OEM required them to lock down their systems.

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
    11. Re:In other words by Anonymous Coward · · Score: 0

      I do not see how my meaning was unclear in any way.

      It wasn't. It was very clear when you said:

      For most Microsoft users opening the case is a non starter any way. This will allow the stupid to have secure computers and the rest of us can do as we please.

      Don't want to be "attacked"? Don't make broad statements that are based on nothing more than your smugness and arrogance.

      By the way, here's an actual attack: The only stupid person here appears to be you.

    12. Re:In other words by houstonbofh · · Score: 1

      The phone is open. The software is not. Kinda like a PC with Windows. And this is a discussion of hardware, right?

      And just to be clear, On Windows, can you uninstall bloatware without admin access? Install new updates? Install Linux without changing the bootloader?

  9. Microsoft's Customers by jaminJay · · Score: 2

    Are Microsoft's customers the OEMs, or consumers. If the former, what incentives would OEMs have to pass the decision on to consumers?

    --
    Leela: "Is all the work done by children?" Alien: "No, not the whipping."
    1. Re:Microsoft's Customers by fuzzyfuzzyfungus · · Score: 2

      "Consumers" are just cattle. Enterprise licensees, though, carry some clout.

      This doesn't help much with cheap consumer systems, or all the various no-you-can't-just-build-one-from-newegg-parts tablets and laptops and other consumer gear; but it does largely ensure that "Enterprise" desktops, laptops, and servers will have some sort of keyfill mechanism, quite possibly offered at an additional cost...

    2. Re:Microsoft's Customers by jaminJay · · Score: 1

      Looks like I'm going to have to start my own hardware company. With blackjack, etc.

      --
      Leela: "Is all the work done by children?" Alien: "No, not the whipping."
    3. Re:Microsoft's Customers by jader3rd · · Score: 1

      The customer is the entity purchasing the OS. So if you buy it in a box, it's the consumer. If it's an OEM purchasing the OS to put into a computer it's the OEM. It's both.

    4. Re:Microsoft's Customers by RogerWilco · · Score: 1

      I think it's one of the key differences between Apple and MS. To MS the customers are the OEMs and corporate IT departments. To Apple the customers are the actual users.

      Neither is perfect, but the difference in focus means I like my Macbook, but my IT department hates Apple's (lack of) support options. For Dell it's the other way around.

      --
      RogerWilco the Adventurous Janitor
    5. Re:Microsoft's Customers by dotancohen · · Score: 1

      Are Microsoft's customers the OEMs, or consumers. If the former, what incentives would OEMs have to pass the decision on to consumers?

      Now is the time to ask them. Write to Dell, write to... no not HP,... who else is left....

      Write to Dell and ask them what they plan to do. Here, I'll help get you started:
      http://support.dell.com/support/topics/global.aspx/support/dellcare/contact_us?c=us&l=en&s=gen&redirect=1

      --
      It is dangerous to be right when the government is wrong.
    6. Re:Microsoft's Customers by Anonymous Coward · · Score: 0

      Go bender

    7. Re:Microsoft's Customers by jbolden · · Score: 1

      I don't agree. I don't think Microsoft views OEM's as customers at all. They view corporate IT departments and the home market as customers. OEM's they view as commodity ancillary device suppliers whom they treat badly.

  10. Microsoft addresses concerns... by Anonymous Coward · · Score: 4, Insightful

    ...by confirming them. Microsoft's customers, the OEMs, will be free to decide who imports keys and how. That's what everybody has been worrying about, isn't it?

    1. Re:Microsoft addresses concerns... by TemporalBeing · · Score: 1

      ...by confirming them. Microsoft's customers, the OEMs, will be free to decide who imports keys and how. That's what everybody has been worrying about, isn't it?

      Exactly. Microsoft does not see the average Windows user as their customer. Rather, they see the OEMs and Big Corporations that purchase Volume Licenses as their customer. In other words (from Microsoft)...Sorry, even though you paid $400 for that Windows license at BestBuy/etc, you're not a customer. Only the OEM who paid $30 for that same license (and bought 5 million of them) is.

      --
      Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
    2. Re:Microsoft addresses concerns... by im_thatoneguy · · Score: 1

      Which is no different the present where the OEM could also put on a bios password and not tell you... but who does that?

  11. I see what you did there... by DontBlameCanada · · Score: 5, Insightful

    Nutshell summary after actually reading the TFA:
            "You can launch any operating system you like, but if you want to benefit from UEFI secure boot protection, you can only launch Windows 8."

    From their screenshots and commentary, there doesn't appear to be any opportunity to add a new "trusted" O/S images to their database. So even signing your secure Red Hat Enterprise Linux won't help you. If you want to use it, you need to turn the bootloader security checks off. The obvious implication, if you want MBR protection you must run Windows 8. Anything else opens the door.

    Yup, Red Hat's take on the situation seems the most accurate.

    1. Re:I see what you did there... by Anonymous Coward · · Score: 1

      You can run any operating system you want, as long as it's black^H^H^H^H^HWindows.

    2. Re:I see what you did there... by Anonymous Coward · · Score: 1

      The blurb is in the comments made by a Microsoft employee:

      UEFI provides the protocol and interfaces to update the databases. Windows 8 supports these new protocols to update the databases in firmware.

      The database is in the firmware, not in Windows 8. Windows 8 will support the UEFI protocols necessary to manage that database, including importing new certificates.

      You obviously can't make use of the UEFI secure boot functionality without having a signed boot loader and trusted certificate. That would be true regardless of Microsoft or Windows 8. Your choices there are to disable the functionality or to find a method through which you can sign and trust your environment. For Linux the solution appears to provide the tools to generate the certificates so that a distro or a self-compiled kernel and be signed and that certificate imported.

    3. Re:I see what you did there... by Anonymous Coward · · Score: 0

      How do you expect UEFI Secure boot to be secure if anybody who wants can make their boot considered secure?

      Was there anything in the article that said only Microsoft was going to be considered secure and everything else would automatically disallowed? My guess, it's up to the OEM and if it ever comes out that OEMs are locking out other OSs, there will be more antitrust lawsuits against Microsoft and possibly the OEM. I don't think they want that again.

    4. Re:I see what you did there... by Renegrade · · Score: 1

      I think the definition of "trusted" is being stretched here.

      The only thing I trust about Windows is that it's going to somehow line Microsoft's wallet with good old-fashioned dollars, directly or indirectly.

      They can't even say the name honestly. Windows 8? Hello? It's an earlier version than Windows 95? It's an upgrade to Windows 3.11? What the hell is wrong with "Windows NT version 6.3" ???

    5. Re:I see what you did there... by synapse7 · · Score: 1
      Wait, but didn't the article state..
      • "Secure boot is a UEFI protocol not a Windows 8 feature"
    6. Re:I see what you did there... by Anonymous Coward · · Score: 0

      I have Linux systems with UEFI that work just fine. IBM HS22V's to be more precise.

    7. Re:I see what you did there... by Anonymous Coward · · Score: 1

      Wait, but didn't the article state..
      "Secure boot is a UEFI protocol not a Windows 8 feature"

      I'm sorry, I fail to see any incompatibility with those statements.

      Secure Boot is a UEFI feature. It existed long before Microsoft made use of it and other OSes already do make use of it. Microsoft is supporting the feature in Windows 8 by implementing these protocols. UEFI includes a protocol for managing the certificate database in firmware and Microsoft is also claiming to be supporting that.

    8. Re:I see what you did there... by Esion+Modnar · · Score: 1

      So this would appear to preclude any possibility to dual-boot Windows 8 and and just about anything else?

      Am I right?

      --

      They say the first thing to go is your penis. Well, it's either that or your brain. I forget which...
    9. Re:I see what you did there... by synapse7 · · Score: 1

      If secure boot is only available when booting Windows8 and must be disabled for anything else, wouldnt that make it a feature? Or does source distinguish features?

    10. Re:I see what you did there... by Anonymous Coward · · Score: 0

      Any OS can make use of UEFI secure boot. It just requires that the boot loader be signed and that certificate be added to the database in firmware. Nothing prevented a Linux distribution from employing this functionality long before Windows 8 was ever announced. Feel free to grab a common certificate or to make your own, sign your boot loader and trust the certificate.

      The new Windows 8 feature is that Windows now supports UEFI Secure Boot whereas previous versions did not and could not be booted in such a fashion at all.

    11. Re:I see what you did there... by Anonymous Coward · · Score: 0

      What's amazing, but after all is the guy's job, is that he managed to write a full length article adding nothing to the debate.
      Hell he even confirmed the main reason to worry, but all the while it's presented as a rebuttal of the previous article !

       

    12. Re:I see what you did there... by jbengt · · Score: 2

      UEFI provides the protocol and interfaces to update the databases. Windows 8 supports these new protocols to update the databases in firmware.

      If you can update the list of certificates and signatures through Windows 8, doesn't that ruin the security of the secure boot?

    13. Re:I see what you did there... by LO0G · · Score: 1

      You could always go read the UEFI Specs to see if the UEFI folks have considered this. My guess is that they have already thought of this and it's answered in the specs somewhere.

    14. Re:I see what you did there... by madhi19 · · Score: 1

      I never met an OEM or a motherboard maker respecting spec or standard!

  12. didn't Stallman... by Anonymous Coward · · Score: 1

    warn us about this years ago?

    1. Re:didn't Stallman... by Anonymous Coward · · Score: 1

      It wasn't exactly a brilliant insight... it's an obvious reality that most people know and understand.

      Anyone can look at where we are heading and predict the bad shit that is coming down the road... it's much more of a challange to actually stop it.

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

      Can't be. As we all know he's an un-american communist-devil who tells nothing but lies about this thing he calls "freedom", yuck!

    3. Re:didn't Stallman... by GameboyRMH · · Score: 4, Interesting

      Stallman is possibly the most prescient (not best by a long shot, but most prescient) sci-fi writer ever. Everyone calls him a nut and then a couple decades later...he was totally, 100% right. Yeah it's not rocket science and he only writes near-future stuff, but still, he has a nearly flawless record.

      --
      "When information is power, privacy is freedom" - Jah-Wren Ryel
    4. Re:didn't Stallman... by houstonbofh · · Score: 2

      He warned us about everything years ago. Literally. By now, GPL2 should have ended the world. Occasionally, he becomes correct. But even a broke clock is correct twice a day.

      I respect the man, and all he has done for software, and computing. But he is far to extreme. The truth is in the middle.

    5. Re:didn't Stallman... by Anonymous Coward · · Score: 0

      I wonder when his stories about pedophilia being perfectly normal and acceptable will come true?

  13. If you can't be bothered to RTF... by neokushan · · Score: 5, Informative

    Just take a look at this image.

    That's all you need to know.

    In Summation: There is a genuinely good reason for enabling secure boot (malware prevention - genuine malware prevention, not just some underhand tactic that's masquerading as malware protection) and as long as your OEM isn't a dick, you should be able to disable it much like how you can disable features in your BIOS today. The decision to remove that ability is down to the OEM, not Microsoft.

    --
    +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    1. Re:If you can't be bothered to RTF... by samjam · · Score: 4, Interesting

      yes. Well put.

      And I want secure TPM booting for my linux/GNU machines too.

      I want a way to install my key, enabled by a physical key & mechanic switch to electrically enable to update operation to write my signing key.

    2. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      If you can disable secure boot with a BIOS setting then how is it providing any malware prevention at all? In order to install itself as boot block code the malware already has to circumvent the security of the OS, at which point it can do more or less anything it likes, including changing the BIOS setting so secure boot is disabled next time the machine starts.

    3. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      You can get anything you want you just have to be willing to pay for it.

    4. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      Disabling the feature in the bios is not a valid solution though. It needs to be made to work with Linux. Now, that support may need to come from the Linux community. Forcing users to give up functionality by running Linux is exactly what MS wants. They want Linux to be a less capable, less desirable alternative.

    5. Re:If you can't be bothered to RTF... by Anrego · · Score: 1

      Hopefully the setting (if they make it available) will be locked down with a jumper on the mainboard, or a DIP switch, or something that is inaccessible to software.

      The amount of stuff happening in changable storage makes me nervous with UEFI.

    6. Re:If you can't be bothered to RTF... by andycal · · Score: 1

      in reality any setting that can be changed by software, is open to modification by rogue software. If the secure boot *can* be disabled, then it's useless. ( if you had to click a hardware switch, that is a different story) I thought M$ push was that this option couldn't be disabled. Or are they planing on the windows boot process to halting if it discovers that it wasn't booted securely? Like that wouldn't get hacked... ( assuming anybody actually wants the new M$ OS by then )

    7. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 1

      Actually you're right.. except where the manufacture decides not to add that option.. you know, like when you open your friend's "BIOS settings" and see that they're different than yours.. or when you get the boot menu with F12 and others with Esc.
      That screenshot might be for one motherboard.. how about the others? any guarantee that Microsoft won't "convince" them not disable such option?

    8. Re:If you can't be bothered to RTF... by Rockoon · · Score: 2

      You are presuming that UEFI settings can be altered post-bootstrap. I dont know if they can or they cannot, but I do know that its possible to prevent. It actually seems kinda trivial to throw a read-only flag that itself becomes read-only right before loading the boot sector.

      --
      "His name was James Damore."
    9. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      EFI stores its nonvolatile variables in flash. Flash can be locked down, even selectively.

      That means, they could lock down the flash region where they store the "secure boot or not"-flag before they start the OS loader, and nothing can revert that change except a reset, which would flush out malware, too.

    10. Re:If you can't be bothered to RTF... by neokushan · · Score: 1

      That screenshot is from the Tablet PC Microsoft themselves gave out at BUILD (before all this kerfuffle actually came up).

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    11. Re:If you can't be bothered to RTF... by neokushan · · Score: 1

      No, Windows will still boot just fine. It has to, otherwise it wouldn't work on older, BIOS-only machines. It's not about "Will windows boot if UEFI security fails", it's more "Will UEFI boot windows if security fails". Windows won't care what's telling it to boot, be it UEFI, Microsoft's own loader, GRUB or whatever, but UEFI will make a distinction about what it's prepared to boot.

      There are also means for the OS (Any OS) to communicate with the UEFI system to determine how secure the boot was. If secure boot does somehow get disabled, Windows will boot just fine but you might get an error or a warning from your Anti-malware client letting you know that the boot couldn't be verified for security.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    12. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      Nonsense. That is true for traditional systems.
      But with a TPM chip, that chip always has the last say about if the setting can be changed.
      If the BIOS changes a flag in the chip to lock things down right before handing things to the bootloader, then not even the BIOS itself could change the setting back without the chip intercepting it.

    13. Re:If you can't be bothered to RTF... by CycleFreak · · Score: 1

      The problem is that the vast majority of users have no idea the BIOS even exists, let alone how to change a setting within the BIOS.

      Meaning that if that if "Secure Boot" is enabled by default, then it will never be changed by the end user. Linux users and computer enthusiasts in general will not have a problem with it. But, honestly, MS doesn't care about that 0.5%.

    14. Re:If you can't be bothered to RTF... by advocate_one · · Score: 2

      Forcing users to give up functionality by running Linux is exactly what MS wants. They want Linux to be a less capable, less desirable alternative.

      Exactly... they want to be able to lock Linux users out of seeing the premium content that will ONLY be viewable on a machine that has been booted and verified as secure to play premium content via their key mechanism... there's even a TPM block shown in the graphic on the article. Don't forget that as far as Microsoft are concerned, their customers aren't the end users, but the film and recording publishers... we're the product... eyeballs delivered to watch the premium content

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    15. Re:If you can't be bothered to RTF... by Rudeboy777 · · Score: 1

      In other words, it's probably not the BIOS that will ship with the final product, and they can remove the ability to toggle that setting at any time in the future.

      --

      From hell's heart I fstab at /dev/hdc

    16. Re:If you can't be bothered to RTF... by neokushan · · Score: 1

      I don't see how that's an issue at all? If you want to install Linux, chances are you're capable of hitting F12 at startup and switching an option off. If you're not capable of doing this, then what the hell are you trying to install another OS for?
      If you don't know about the option or BIOS, why would you want to disable it?

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    17. Re:If you can't be bothered to RTF... by neokushan · · Score: 1, Troll

      Yes and they can also superimpose the windows logo on top of the screen so it's permanently there, no matter what you use it for. They could also install a flash chip that wipes the hard drive and installs windows every time you press the Windows key. They could also make it play a "BILL GATES OWNZ YOU!!!!" soundbyte upon startup. There's all sorts of things they could do, but that doesn't mean they'll do it. As has been stated several times before, all the Linux doomsday prophesies rely on the OEM removing the ability, not Microsoft. Until something actually happens in this regard, it's pure FUD and scaremongering from people who either just want to bash Microsoft for the sake of bashing them, or idiots who simply don't know any better. Or both.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    18. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      And you're welcome to develop those features yourself.

    19. Re:If you can't be bothered to RTF... by IGnatius+T+Foobar · · Score: 1

      The image shows a computer that allows you to switch UEFI secure boot off and on.

      And that's great, as long as every computer offers this option. The danger is that in the not too distant future, OEM's may start building computers that don't have that option. It may be attractive for them to build computers that are "locked" in the same way that many phones are locked. It is up to us in the free world to continue to raise a big stink to make sure that doesn't happen, at least not without a fight.

      --
      Tired of FB/Google censorship? Visit UNCENSORED!
    20. Re:If you can't be bothered to RTF... by HermMunster · · Score: 1

      If you disable it then it is not genuine prevention any longer? If you disable it then win8 no longer boots. Microsoft get governments to consider it as part of the bid process and gets the governments to put it in the contracts. Certification takes significantly longer for non Microsoft products thus giving Microsoft the competitive advantage. If a contractor seems to be close they can slow down certification till they get the bid.

      This is rife with abuse potential.

      --
      You can lead a man with reason but you can't make him think.
    21. Re:If you can't be bothered to RTF... by neokushan · · Score: 2, Informative

      You know something? I completely, utterly and wholeheartedly agree with this.

      What I'm trying to get at is that everyone is jumping on Microsoft for this, when really it has little to do with them (aside from mandating that UEFI secure boot be enabled by default). Microsoft could turn around tomorrow and say "no actually it's fine, we don't want secure boot by default" and the situation wouldn't be any different at all - OEMs could still enable it and remove the option to disable it.
      Using your phone example - Google in no way demands that bootloaders be locked (and their own branded phones don't lock them), yet many manufacturers still do it. I really don't get why Microsoft keeps getting dragged into this when it's the OEMs you should be fighting.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    22. Re:If you can't be bothered to RTF... by neokushan · · Score: 3, Insightful

      If you disable it then it is not genuine prevention any longer? If you disable it then win8 no longer boots.

      Incorrect.

      This seems to be a common misunderstanding with the whole thing. Windows will boot no matter what, be it secure or unsecure. It's not Windows' decision, it's the UEFI system's decision if it should boot windows, Linux or whatever.

      The whole point of the secure boot is to prevent malware that fucks with the bootloader, allowing rootkits to be inserted into the Kernel before any anti-malware gets a chance to run.

      This is how a chain of trust works.

      A -> B -> C -> D

      A, ideally, is some hardcoded software that cannot be modified. In games consoles, it's usually a part of a ROM or in the Xbox-360's case, it's on the CPU itself. It checks that B hasn't been modified in any way, shape or form and if it passes, boots it. B then does the same for C and so on and so forth.

      The principal is exactly the same here. If you disable UEFI secure, all you're doing is saying "Dear A, don't bother checking B, just boot the fucking thing". B will then happily continue on as normal, booting C which then boots D. At some point, D can look back and check that A, B and C haven't been modified but it's almost pointless because if they've already been compromised, they'll feed the next in the chain whatever the fuck the compromiser wants it to.

      A = UEFI bootloader
      B = Windows Bootloader
      C = Windows
      D = Anti-malware

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    23. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      Until something actually happens in this regard, it's pure FUD and scaremongering from people who either just want to bash Microsoft for the sake of bashing them, or idiots who simply don't know any better. Or both.

      Quick question, how many court cases has Microsoft lost, then settled and had sealed? 5, 10, 15? Its not FUD.

    24. Re:If you can't be bothered to RTF... by CycleFreak · · Score: 1

      Uh ... That's my point exactly.

    25. Re:If you can't be bothered to RTF... by TheSunborn · · Score: 0

      Except that Windows can't boot if you disable secure boot. So dual booting will be really fucked up.

    26. Re:If you can't be bothered to RTF... by bigstrat2003 · · Score: 1

      If you disable it then it is not genuine prevention any longer? If you disable it then win8 no longer boots.

      This is patently false. Secure boot being on by default is required for the special "built for Windows 8" logo, not for Windows 8 to boot at all.

      --
      "16MB (fuck off, MiB fascists)" - The Mighty Buzzard
    27. Re:If you can't be bothered to RTF... by neokushan · · Score: 1

      Read the rest of the thread, this has been discussed at least 3 times now: You are Wrong.

      Windows will boot with secure boot disabled. All secure boot does is ensure that Windows hasn't been modified before UEFI tries to boot it. If you modify windows, secure boot will prevent it from booting. If you disable secure boot, both modified and unmodified windows installs will boot.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    28. Re:If you can't be bothered to RTF... by malevolentjelly · · Score: 2

      Maybe you should only buy computers that allow you to disable secure boot then. Or is that too obvious and uncontroversial?

    29. Re:If you can't be bothered to RTF... by dkleinsc · · Score: 2

      as long as your OEM isn't a dick

      That's a pretty big assumption right there.

      And I should point out, this isn't just Dell or HP or Lenovo or something, it's also motherboard manufacturers who can get in on this game.

      --
      I am officially gone from /. Long live http://www.soylentnews.com/
    30. Re:If you can't be bothered to RTF... by cdrudge · · Score: 2

      What I'm trying to get at is that everyone is jumping on Microsoft for this, when really it has little to do with them (aside from mandating that UEFI secure boot be enabled by default). Microsoft

      And they aren't mandating UEFI secure boot be enabled by default. They are only mandating it if you want to put a little sticker on the device that says "Designed for Windows 8".

      If you are buying a PC because it has a little sticker on the device that says Windows 8, then you are almost guaranteed to be in the group that could care less whether it's enabled or not as you aren't going to be putting Linux, OpenBSD, etc on it.

    31. Re:If you can't be bothered to RTF... by neokushan · · Score: 1

      Here, if you don't believe me, check this image out or this post on the BUILD blog.

      @Jose Pedro Of course Windows is usable without secure boot -- just like the post stated :-)

      How secure boot works with any other operating systems is obviously a question for those OS products :-) We focus our boot loader on Windows and there are a number of alternatives for people who wish to have other sets of functionality.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    32. Re:If you can't be bothered to RTF... by AngryDill · · Score: 2

      If Microsoft were truly "not evil" as its apologists claim, they would address the concerns of consumers by making it a requirement that the OEM provide the key to the buyer as a prerequisite for being "Windows 8" certified.

      --


      I'm Erwin Schrodinger and I approve of this message, and I do not approve of this message!
    33. Re:If you can't be bothered to RTF... by neokushan · · Score: 1

      At no point has anyone here stated that Microsoft is not evil. Yes, I'm defending them in this instance but that's purely because they're not to blame for OEM's potentially being shitty. The OEMs are (potentially) to blame for that.
      There's plenty of things Microsoft has done wrong that you can blame them for, but it's counter-productive to rag on them for stuff that has nothing to do with them (like this secure boot malarky), it's just a waste of time.

      Speak with your wallets, there's plenty of manufacturers out there, giving you plenty of choice. The chances of them all removing a feature like this is pretty slim so just do a bit of research before you buy a new PC. If you got caught out, email your vendor for a BIOS update (or whatever the hell the UEFI equivalent will be). If that doesn't work, complain, start a site that lists OEMs based on how shitty they are, do the usual stuff, but at no point should you blame Microsoft for a decision they've left to the OEM.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    34. Re:If you can't be bothered to RTF... by nschubach · · Score: 2

      The problem is that the number of Best Buy computer purchasers outnumber the number of us. There's little incentive for HP/Dell/etc. to continue supplying non-locked systems. Eventually, it'll be build it yourself expecting to put non-Windows in it or you'll never put anything but Windows in it. What would encourage a person going off to college to investigate if their PC could load Linux beforehand? When said student finds out about Linux... are you saying they should also be required to build a new PC? That's a much steeper learning curve than putting in a disc and hitting "go".

      --
      Every time I start to have faith in humanity, I ruin it by driving to work between 7 and 8 am.
    35. Re:If you can't be bothered to RTF... by malevolentjelly · · Score: 1

      If people can run Linux on PS3's, then chances are pretty good they will find a way to insecurely boot Linux on their PC's if they would rather screw with conf files than study. On the other hand, there's still no indication that the ability to disable secure boot will be widely unavailable-- the only example you have of a computer with secure boot currently allows it to be disabled. Are you just anonymously angry about the way you imagine computing to be if it goes in such a way that might upset you?

    36. Re:If you can't be bothered to RTF... by SuricouRaven · · Score: 1

      "as long as your OEM isn't a dick"

      That's a very significent conditional.

    37. Re:If you can't be bothered to RTF... by StuartHankins · · Score: 1

      Hey if you're going to be another Microsoft apologist, at least man up enough to admit it. There's no way you could know the history and come to the same "nothing to see here" conclusion. Unless you're a troll, in which case I say, "Good job, you got me."

    38. Re:If you can't be bothered to RTF... by http · · Score: 2

      Why? Some of us have working memories.
      Microsoft would love nothing more than to lock out other operating systems at the hardware level, and the bootloader is the critical first step. Why isn't 55% of the computing world using BeOS? Because MS controlled the bootloader via OEM contracts, possible only because of their monopoly position.

      "I once preached peaceful coexistence with Windows. You may laugh at my expense -- I deserve it."
      --Jean-Louis Gassée, CEO of Be

      I believe the reason we will have to fight OEMs is because MS will tell them, "Unlockable UEFI? bulk rate = $35. Locked? bulk rate = $22

      As for the phones, what monopoly has Google ever had on the phone market?

      --
      If opportunity came disguised as temptation, one knock would be enough.
      3^2 * 67^1 * 977^1
    39. Re:If you can't be bothered to RTF... by neokushan · · Score: 1

      What and I can't do a "nothing to see here yet?
      We can debate all day on the future and what Microsoft may do or we can stick to the here and now and stick to the facts at hand.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    40. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      No, it absolutely is FUD, and it comes up every single time Microsoft has ever implemented a feature that permits preventing some forms of software from running. It's something that Slashdot has been spewing for as long as it has existed. Go read Slashdot archives over Group Policies in Windows 2000, or driver signing in Windows XP, or Palladium, or BitLocker, or any of the other obvious avenues that would be exploited for the sole reason to piss off twelve kids in a basement because clearly they'd have no other purpose. None of these sensationalist fears have ever played out, but if you are concerned about how much control you have over the hardware you buy you should probably look closer at what Microsoft's competitors have been doing to lock you out instead.

    41. Re:If you can't be bothered to RTF... by 0123456 · · Score: 3, Insightful

      If you are buying a PC because it has a little sticker on the device that says Windows 8, then you are almost guaranteed to be in the group that could care less whether it's enabled or not as you aren't going to be putting Linux, OpenBSD, etc on it.

      How many motherboard and hardware manufacturers do you think there are who don't want to be able to put a 'Designed for Windows 8' sticker on the box?

      When Microsoft says your hardware must lock out Linux to get that magic sticker, manufacturers will lock out Linux.

    42. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      In Summation: There is a genuinely good reason for enabling secure boot (malware prevention - genuine malware prevention, not just some underhand tactic that's masquerading as malware protection) and as long as your OEM isn't a dick, you should be able to disable it much like how you can disable features in your BIOS today. The decision to remove that ability is down to the OEM, not Microsoft.

      Hey, let me bring that to the forefront a bit more...

      [...] and as long as your OEM isn't a dick [...]

      Yeah, that's the part. I felt the need to highlight that because it's pretty obvious you just slipped that in there as if we weren't supposed to notice the little caveat to your feel-good summation.

      Well, okay, I take that back.

      It's certainly not a little caveat at all.

    43. Re:If you can't be bothered to RTF... by jedidiah · · Score: 1

      Reading the nonsense would not make it any more plausible.

      Even if it's not intentional, this is yet another classic case of Microsoft engineering something with horribly unintended consequences because they seem to have a complete inability to think things through or think outside the box in the slightest.

      Accusing Microsoft of active malice is probably giving them more credit actually.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    44. Re:If you can't be bothered to RTF... by Dr_Barnowl · · Score: 1

      Yeah, but what vendor isn't going to want aim at that market? They are the majority. Therefore every vendor will be striving to qualify.

    45. Re:If you can't be bothered to RTF... by BJ_Covert_Action · · Score: 2

      Well, Microsoft tends to have a bad history of passive-aggressively fucking people. I am not particularly knowledgeable when it comes to low-level computing stuff like this, but here is what I think a lot of folks are worried about:

      1) Microsoft says Windows 8 will need secure boot to boot.
      2) Microsoft says OEMs are responsible for allowing the end-user to enable or disable secure boot.
      3) Microsoft, behind closed doors, tells numerous OEM vendors, "Yeah, you're welcome to offer hardware that allows the end user to disable secure boot, but if you do that, we aren't going to sell you Windows 8 licenses that you can package with your hardware. Good luck selling computers to people without a copy of the most widely recognized brand of operating system preinstalled on it."
      4) In response, OEMs say, "Shit fuck! If we can't offer people new Windows 8 computers, most people are going to see our computers as exotic or out-of-date! We better make it impossible to disable secure boot so that we can continute to package the latest and greatest Windows OS out there!"
      5) 95% of computer users now buy computers from trusted OEMs but cannot install or implement Linux when they finally decide, "Fuck this, Microsoft has shit in my oatmeal for the last time, I am going to pick up that weird Linux shit my roomate keeps rambling about."
      6) And, thus, Linux adoption gets heavily curtailed because a large segment of would-be Linux users no longer have the option of installing Linux because they didn't know about an obscure-ass issue a year ago when they first bought their computer.

      From what I can tell, that still seems like an entirely plausible situation.

    46. Re:If you can't be bothered to RTF... by bws111 · · Score: 1

      Yeah, except that it was Intel (not Microsoft) that invented it about 15 years ago. Oh, and Linux has supported it since 2000. As does HP-UX, openVMS, and Apple. Now, finally, MS is using it, and somehow it magically became EVIL.

    47. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      you computer experts should be able to disable it much like how you can disable features in your BIOS today

      There, fixed it for you.

      Bottom line, the average computer buyer is not going to be able to get into their BIOS and make the change to allow anything other than Win8. This is nothing more than a way to lock-out alternatives for the average computer user.

    48. Re:If you can't be bothered to RTF... by letsief · · Score: 1

      Then I have great news for you! At least, for your first wish. If all you want is a TPM-based trusted boot, then you can do that today. A TPM-based trusted boot just stores hashes of the BIOS, option ROMs, boot loader, etc., executed during boot. You can later access those hashes, and report the hashes to another server (signed by the TPM, of course, so you can't fake them).

      UEFI secure boot doesn't use a TPM. The UEFI BIOS will verify option ROMs and boot loaders prior to executing them. A TPM isn't very useful for doing that, and therefore isn't used. Of course, if there is a TPM, Microsoft will happily store hashes of its critical system files on the TPM during the boot process, and it can access those hashes (and hashes the BIOS, opROMs, etc.) later on.

      Your second wish is possible, but don't hold your breath.

    49. Re:If you can't be bothered to RTF... by letsief · · Score: 1

      I agree the on/off setting for secure boot should be locked down after boot, but the list of trusted certificates is explicitly intended to be modifiable after boot. It's basically implemented with UEFI authenticated variables (i.e., signed variables). The OS (or some application running on the OS), it supposed to be able to overwrite an authenticated variable by supplying a new, properly signed string. The UEFI BIOS will verify the signature on the newly supplied string prior to overwriting the variable.

    50. Re:If you can't be bothered to RTF... by jbolden · · Score: 1

      I don't think the film companies care about Linux, they are about DRM. And of course they would like a situation of more DRMed platforms. And Microsoft has been talking for almost a decade of trying to provide a secure home DRMed solution that still can run most Windows software.

      There is nothing to stop a DRMed Linux from existing other than that the GPL would likely require the encryption code to be in hardware.

    51. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      "There is a genuinely good reason for enabling secure boot (malware prevention - genuine malware prevention, not just some underhand tactic that's masquerading as malware protection)..." by neokushan (932374)

      You're delusional or a shill... The OS itself is what's responsible for malware and root kits being able to exploit it. The claim that the system now needs hardware lockouts to prevent this is ludicrous. UEFI and you can both go to hell.

    52. Re:If you can't be bothered to RTF... by TheSpoom · · Score: 1

      The nice thing about the Wii is that (per your analogy) A's checking of B was broken so we could insert our own second level code in the boot process. They fixed it in later generation consoles but since it was in ROM, earlier consoles are permanently vulnerable. It works both ways.

      --
      It's better to vote for what you want and not get it than to vote for what you don't want and get it.
      - E. Debs
    53. Re:If you can't be bothered to RTF... by Anonymous Coward · · Score: 0

      yes. Well put.

      And I want secure TPM booting for my linux/GNU machines too.

      I want a way to install my key, enabled by a physical key & mechanic switch to electrically enable to update operation to write my signing key.

      Get a ChromeBook then.

    54. Re:If you can't be bothered to RTF... by TangoMargarine · · Score: 1

      Or are they planing on the windows boot process to halting if it discovers that it wasn't booted securely? Like that wouldn't get hacked... ( assuming anybody actually wants the new M$ OS by then )

      Not that that would actually be a big problem, as long as you can toggle the Authenticated Boot setting; just turn it off whenever you want to boot something other than Windows and then back on after. Maybe they can even figure out a way to make GRUB do it automatically.

      --
      Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
    55. Re:If you can't be bothered to RTF... by Bengie · · Score: 1

      "by making it a requirement that the OEM provide the key to the buyer"

      So a malware creator can use that key to create signed malware?

      There is a reason we call it a "private" key. If you don't like it, make your own key and import it.

  14. Realistically all the need is a clear boot warning by Chrisq · · Score: 1
    If they modified the standard so that the system would give a confirmation popup saying

    "You are about to load an unsigned operating system, do you want to do so? To continue may compromise the security of your system.

    This way people could load Linux if they wanted but the "joe average" would know something is wrong if he was compromised by a boot virus. This would actually be more sensible than preventing other systems, otherwise they will have literally thousands of hackers trying to discover the boot signing keys and publish them online like they did for blue-ray.

  15. Time to get my last notebook by Anonymous Coward · · Score: 0

    As long as I can build my own box, UEFI won't be a problem. But I bet most notebook manufacturers will lock their products down, for easier support.
    And even if they put a Linux on their notebook, they may want to lock that down.

    1. Re:Time to get my last notebook by SuricouRaven · · Score: 1

      Probably not so much notebooks as tablets. Similar reasons as with mobile phones. Lockdown OS means lower support costs and the options of disabling features at the behest of the networks or bundling spyware or adware that the user can't remove.

  16. if they wanted to address the concern by Anonymous Coward · · Score: 1

    If they wanted to address the concern, they would have made user control a requirement of the Windows Certificate program. The worry from the Linux crowd is that manufacturers have historically only done the minimum required in order to get Windows working.

    "For the enthusiast who wants to run older operating systems, the option is there to allow you to make that decision."
    - Is there some sort of policy on these blogs that prevents them from mentioning their competition?

    1. Re:if they wanted to address the concern by NatasRevol · · Score: 1

      - Is there some sort of policy on these blogs that prevents them from mentioning their competition?

      Yes.

      http://www.marco.org/2011/09/16/some-other-tablets-you-may-have-seen

      --
      There are two types of people in the world: Those who crave closure
  17. Pass the FUD, I'm starving. by The+Altruist · · Score: 1

    Guys, remember the Internet Explorer anti-trust controversy?

    *long awkward pause*

    They. Are. Not. Going. To.

    And even if they did, so what? Seriously, this is frickin' Slashdot. All of you either build your own machines or own Macs.

    1. Re:Pass the FUD, I'm starving. by Anonymous Coward · · Score: 0

      >implying there is a difference between a modern mac and a home-built PC at the hardware level.

    2. Re:Pass the FUD, I'm starving. by The+Altruist · · Score: 1

      Yeah, about $1000.

    3. Re:Pass the FUD, I'm starving. by Svartalf · · Score: 3, Interesting

      Building your own machines will be a bit of a problem if all the new motherboards do the same thing. Do you honestly think the DIY vendors will not march to that drum unless they're gunning for the Linux user crowd in the first place?

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
    4. Re:Pass the FUD, I'm starving. by Renegrade · · Score: 1

      I can totally see Asus having those features installed, and giving it some silly Asus name. "Super SafeBoot Deluxe!"

      On the other hand, they will allow users to disable it in the "Boot" section of the BIOS setup.

      Super SafeBoot Deluxe [No ]

      (Description: "Enable/disable Super SafeBoot Deluxe" -- not very helpful).

    5. Re:Pass the FUD, I'm starving. by Anonymous Coward · · Score: 0

      Know what's next? MS offers OEMs a huge discount to lockout the ability to run un-secured. Honestly a hardware key (dip switch) to allow private keys is not that hard. Maybe reviewer sites should flag these machines as they come out.

      "Seriously, this is frickin' Slashdot. All of you either build your own machines or own Macs" or we extend the life of an old PC by adding Linux to it.

    6. Re:Pass the FUD, I'm starving. by Anonymous Coward · · Score: 0

      1999 called, they want their prices back.

      For $1000, you can get a 11" MacBook Air. Can you build one of those for free?

    7. Re:Pass the FUD, I'm starving. by Anonymous Coward · · Score: 0

      (Posting anon since I've been moderating here)
      Microsoft is setting a standard to use their software that *will* effect Linux in *many* cases... sure they can gnaw and mash about OEM responsibility, but at the same time they will be denying Windows Logo stickers for vendors that don't enable secureboot. It's the corporate version of "talk softly and cary a big stick" diplomacy.

      Users will be at the mercy of OEM's to provide a special case for anything that is not Win8 due to Microsoft requirements... how is this not clear? Wanna run Win Server on that laptop for testing... not authorized buddy. Wanna test out Ubuntu? NYET! How about Win7? NEIN!

      Here's the glorious choices given:

      Nick 22 Sep 2011 11:47 PM #
      I notice that you're careful to avoid directly saying that customers will actually be able to manage UEFI certificates on non-developer hardware. For example:

      "Microsoft supports OEMs having the flexibility to decide who manages security certificates and how to allow customers to import and manage those certificates"

      So will customers be getting that access or won't they?

      Microsoft responds:

      @Nick We accurately stated that such decisions are left to the OEM. There may be good reasons why certain enterprises may not want PCs that can be configured in such a way, and there may be good reasons why an OEM or white box retailer may choose to allow that flexiblity for their customers. It's all about choice and flexibility.

      Other than the possibility of completely disabling secure boot, what choice and flexibility are we going to get? My experience points to no choices for the majority of consumers.

      As a security engineer I think this is just awful. The RIGHT choice would be to allow the user to cryptographically sign (DSA) their MBR/Bootloaderm, and store the signatures safely in the bios or TPM chip. Consumer PC's would be signed during first load and delivered secured. Enterprise admins should be able to sign and manage these signatures remotely with the vendor tools. This would give 99% of the users the security they want without exposing boot signatures to the OS itself - which is where the danger lies in the first place!! The OS is NOT the place to be exposing these signatures!!!

      It would also be backwards compatible with existing OS's such as Win7, Vista and *gasp* XP... which is an interesting tactic given the long-lived and frustrating XP user-base. If choosing your OS is more painful than a CD load, then chances are they won't go back to Win7, WinXP, or Linux. Winning!!

      Lastly, having the ability to manage boot certificates through the OS is a terrible idea... root kits have RING 0 access!! Did they honestly forget that kernel-level privileges would prevent access to the certificates? Might as well stick your fingers in your ears and yell NYA NYA NYA.

    8. Re:Pass the FUD, I'm starving. by bws111 · · Score: 1

      I don't see how your 'right' way is any different from what actually happens, and nothing in those quotes indicates otherwise.

    9. Re:Pass the FUD, I'm starving. by SuricouRaven · · Score: 1

      This is funnier for me, as right now I am pondering a laptop in front of me and the BIOS option 'boot booster.' What does it do? Havn't the faintest. Setup screen doesn't say. Manual doesn't say. I do know that after I wipe the drive and install XP (For our network management software won't support anything newer) it start putting up a message in POST complaining that boot booster failed.

    10. Re:Pass the FUD, I'm starving. by Hatta · · Score: 1

      The IE anti-trust cases came before Microsoft starting making large political donations. Microsoft learned its lesson, greased the right palms, and is back to abusing it's monopoly position as much as it ever did.

      --
      Give me Classic Slashdot or give me death!
    11. Re:Pass the FUD, I'm starving. by Anonymous Coward · · Score: 0

      The difference is as follows:
      * Microsoft will generate keys and give them to the OEM vendor before installation of the OS. If one of the signature keys is leaked, then viruses may be crafted to exploit vulnerabilities in the firmware, perhaps disabling or bricking the machine.
      * The OEM may or may not accept other vendor's hardware or OS keys, The proposed solution is to disable secureboot - thus allowing viruses and root kits to overwrite MBR's and bootloaders.
      * When hardware needs reparing or replacement, the user must get OEM approved hardware which conforms to the keys the firmware will accept; or the user must disable secureboot.

      The right way is as follows:
      * The user, enterprise admin, or OEM will generate the keys at OS load time, the keys will always be different and should never leave the secure firmware. This prevents leaked OEM or MS keys and signatures from being used in malware.
      * The OEM doesn't have to keep track and accept other vendor's keys, the firmware is given a known-good configuration and signs it before the user ever logs into the system.
      * The user or enterprise admin can choose when to sign a good configuration. When a video card or harddrive is replaced the user doesn't need to get permission from the OEM to use non-ORM hardware. It is replaced and the new configuration is signed.

      Hope this helps.

    12. Re:Pass the FUD, I'm starving. by bws111 · · Score: 1

      Egad that is awful. You have just switched from "this is trusted becomes it comes from someone I trust" to "this is trusted because I said so". And how, exactly, is the average consumer supposed to know just what to trust? Your method is no more secure than the status quo, which is not secure at all.

    13. Re:Pass the FUD, I'm starving. by Anonymous Coward · · Score: 0

      The average consumer will get a machine that is already installed and signed with a unique key - once that key is forcefully obtained you only own a single machine. The amount of work to crack that key would be astronomically huge in the case of DSA or RSA signatures.

      Trusting the vendor to secure a signing key is safer you think? If a vendor key is leaked or broken then you have no trust in the secureboot process. The value of that signing key is worth all the machines that accept the key, which makes it a huge target. If only one bios somehow leaks the key then all the machines with that key are now insecure. A good hardware hacker will get that key, just look at the PS3, Wii, and other Vendor-supplied key signature & encryption schemes which have failed.

      Just comparing the value of owning a single machine versus the value of owning all the vendor's machines is certainly worrying to me.

    14. Re:Pass the FUD, I'm starving. by bws111 · · Score: 1

      What are you talking about? How is a bios going to 'leak' a key? The keys are public, that is the whole point of them.

      Here is my understanding of how this works: A vendor has a piece of code it wants you to trust (bootloader). The vendor creates a public/private key pair, and distributes the public key to all it's users. It uses the private key to sign the piece of code, and the signature gets distributed with the code. When UEFI is ready to load the bootloader, it uses the public key to verify that the signature is still correct on the code (the code has not changed since the vendor signed it). If the signature is good, boot proceeds as normal. If the vendor subsequently updates the code, the new code is again signed with the same key, and everything works as expected. If a piece of malware modifies the bootloader the signature will not match and booting is halted.

      In this scenario there are basically three things that can go wrong: the signer of the code (ie the original vendor) can sign code with malware in it, the signer of the code can lose the private key, allowing anyone to sign invalid code, and the public key you have could be bogus. The first two would remove the vendor from the 'trusted' category, so any further discussion of trust is moot. The third one (bogus key) should be relatively easy to prevent (vendor has a SSL-protected web site that contains the key).

      I am not sure what happens with your plan. Let's say you (a consumer) buy a new Dell PC at Best Buy (or a new no-name box from PCs-R-Us that comes with a copy of an OS). I think you said you would generate the signature on first boot, right? Well what happens if the code has already been compromised by the OEM, the retailer, the shipping company etc? You just said to trust code that can't be trusted. What happens when the vendor OR malware updates the code, making your signature invalid? Do you expect your users to fully understand the nature of the change, and re-sign the code? If they could do that, we wouldn't need to have this discussion in the first place.

      In the UEFI method, a leaked or broken key would be bad. However, that is a pretty unlikely scenario. Even if it does happen, you could get the word out that the boot process is no longer secure, contact your vendor for a fix, etc.

      In your scenario you have no protection at all, ever. It is no different than today, because you are trusting too many people along the way. Including, most worryingly, the end users.

    15. Re:Pass the FUD, I'm starving. by Anonymous Coward · · Score: 0

      In this scenario there are basically three things that can go wrong: the signer of the code (ie the original vendor) can sign code with malware in it,

      This is the same thing as the user signing a piece of malware - which they would have to reboot into the BIOS and do manually. Microsoft is advocating kernel level access to the BIOS private/public keys... which may allow root-kits to sign themselves.

      However, if a bootloader modification occurs in either case, it will be detected and in both cases will have to be dealt with in exactly the same way. Reinstallation. If you're using a Vendor keypair then you have to trust that a hacker has not gained access to the Vendor's private keys.

      A break of a unique User keypair is not going to let a virus sweep through a company with the same keypair and "own" lots of machines undetected.

      the signer of the code can lose the private key, allowing anyone to sign invalid code,

      Not a real issue - but if the user signed their own code then this would happen far less - because the user can't access the private key without pulling the BIOS flash or other hardware hacking tricks such as tweaking the bus.

      and the public key you have could be bogus.

      Again, not an issue with self-signed code. It lives securely in a protected area of the BIOS which is offline after POST.

      The first two would remove the vendor from the 'trusted' category,

      Vendors loose control of their super-secure private keys all the time... Apple iPhone, BluRay, PS3, XBox, Wii, TI calculators, Comodo, Diginotar, RSA, Booze-Allen, etc. A "One Key to Rule The All" scheme is a massive target with a substantial payoff in the wrong hands.

      I am not sure what happens with your plan. Let's say you (a consumer) buy a new Dell PC at Best Buy (or a new no-name box from PCs-R-Us that comes with a copy of an OS). I think you said you would generate the signature on first boot, right? Well what happens if the code has already been compromised by the OEM, the retailer, the shipping company etc?

      Physical possession or availability of a machine to an adversary is always considered a major security issue. You have to trust the Vendor in either case. But with Vendor signed keys your trust must extend for the entire life of ALL your machines from that vendor, whereas User generated keys are unique, self-trusted and resettable. Due to the key uniqueness, keypair attacks are nearly impossible - and even if it was possible, brute forcing a keypair only yields a single machine at a time.

      You just said to trust code that can't be trusted. What happens when the vendor OR malware updates the code, making your signature invalid? Do you expect your users to fully understand the nature of the change, and re-sign the code? If they could do that, we wouldn't need to have this discussion in the first place.

      Again - the result is the same. If the signature is invalid with either Vendor or User keypair types then you must wipe the machine and reinstall. IT'S TOO LATE - SecureBoot only detects that something bad already happened. Where you get your support is not my concern.

      My concern is that if the Vendor keypair has been stolen then you won't know! If you have 5 machines with the same Vendor keypair, then all 5 will have submarine code. The attacker only needed ONE keypair to do this.

      On the other hand, if you had used user keypairs, then the attacker would have to break all 5 machines first before they could plant submarine code on all the machiens. That's much, much harder.

      Thanks, it's been an interesting discussion.

    16. Re:Pass the FUD, I'm starving. by Renegrade · · Score: 1

      Heh, that's totally ASUS-like.

      Nice systems, documentation which is only so-so at best.

    17. Re:Pass the FUD, I'm starving. by SuricouRaven · · Score: 1

      The laptop is indeed an Asus. One of those Eee netbooks.

    18. Re:Pass the FUD, I'm starving. by mcgrew · · Score: 1

      It's kind of hard to make your own laptop. Getting Linux on a notebook that has no optical drive is hard enough as it is, this will make it worse.

      Non-tech friends bring me broken computers, I always install Linux on them dual boot (if Windows isn't so hosed as to be unrepairable and they've lost the disk or magic number) and tell them to NOT get on the internet in Windows.

  18. Re:Realistically all the need is a clear boot warn by scottuss · · Score: 1

    Yes, because all "Joe Average" people are going to then panic and power off their computers. Most "normal" users that I know would look at that, shrug their shoulders and hit "continue", wanting to get on with watching their DVD, writing their letter, browsing the web, etc etc.

  19. Re:Realistically all the need is a clear boot warn by tires+don+exits · · Score: 1
  20. This isn't Microsoft by Murdoch5 · · Score: 2
    This has nothing to do with Microsoft, the fact that Windows 8 will use UEFI is a choice just like any other choice. Linux supports UEFI,

    Linux has been able to use EFI at boot time since early 2000, using the elilo EFI boot loader or, more recently, EFI versions of GRUB.[21]

    Which is from the UEFI wiki page and Linux documentation. The issue is that the boot might be locked, not that Windows 8 will find and delete Linux partitions, so really this has nothing to do with Microsoft, it has to do with OEM systems. If your concerned about this effecting you then build your own computer and it wont matter.

    1. Re:This isn't Microsoft by sakdoctor · · Score: 2

      Stop spoiling this 2 minute hate on Microsoft with your facts.

    2. Re:This isn't Microsoft by Anonymous Coward · · Score: 1

      But you can't (realistically) build your own motherboard...even if a bunch of us got together and did exactly that, we couldn't make a motherboard that was remotely cost-competitive with the big manufacturers.

      So we're stuck with motherboards with this instead of the regular BIOS...and that's where the problem lies.

    3. Re:This isn't Microsoft by Lonewolf666 · · Score: 1

      I think the non-Windows market is large enough these days that at least one or two motherboard manufacturers will make boards where the user has a way to disable "Secure Boot" or add his own keys.

      These may be more expensive though...
      I could imagine that this last refuge is in the market for server hardware, and instead of a $100 ASUS, you'd have to buy a $250 Tyan or such :-(

      --
      C - the footgun of programming languages
    4. Re:This isn't Microsoft by WorBlux · · Score: 1

      I'm fairly sure 3.1 or 3.2 will have a kernel config option where you can build an efi stub for the kernel, that is just let efi boot your kernel directly. Signing may not be far behind.

  21. Re:Realistically all the need is a clear boot warn by SuricouRaven · · Score: 2

    That's what it does right now, in the demo hardware. If you want to run anything other than Windows 8, you just have to go untick an option in the setup screen. The big fear of slashdotters is that once this is supported in hardware, it would be so, so easy for an OEM to remove that option, and they may well do so under pressure either from Microsoft or possibly as part of a data-collection/adware/network-locking subsidy deal similar to that already frequently seen in the mobile phone sector, where firmware-locking is the norm. Think Windows tablets more than desktops.

  22. This is damaging to FOSS by Beetjebrak · · Score: 1

    Of course a Linux or other OS user might be able to disable this "feature" but that would *SERIOUSLY* tarnish the reputation of said OS. If it can not use "Secure boot" -for whatever reason- that implies it boots insecurely.. oh the horror!! It will put the adoption of any kind of grassroots OS at a major disadvantage. For us tinkerers here it's an absolute outrage that the freedom to tinker will come at a premium in the near future, but we've always been the minority.

    --
    Learn from the mistakes of others. There isn't enough time to make them all yourself.
  23. Answer from Matthew Garret to this article by diegocg · · Score: 1

    "Microsoft wrote an article about how they weren't making it harder to install Linux which described, in detail, how they're making it harder to install Linux. Here's my response" - https://plus.google.com/109386511629819124958/posts/GXc9y7E5uZX

  24. Re:Realistically all the need is a clear boot warn by icebraining · · Score: 1

    You're assuming there is such an option, and that the user won't be required to reboot, enter the menu and disable secure booting.

  25. pay to play by Anonymous Coward · · Score: 0

    yeah i only need a certificate to boot, but who issues that certificate and how much ? let me guess it will be to be a the same gang of suits that signs websites.
    the free money game just doesnt get any harder for these guys

    ill just wait till the antitrust lawsuits start happening, as soon as MS sign their bootloader is the time to strike,
    locking out the competition 1x$500 boot certificate at a time

    1. Re:pay to play by SuricouRaven · · Score: 1

      It'll be the OEMs, or more likely the BIOS vendors. They are obviously going to sign Windows, but may or may not think linux worth the effort - and even if they do, they couldn't possibly sign every kernel for every distro, or even every version of GRUB. Not that they will sign GRUB at all, because it could then go on to load untrusted malware.

  26. Yes, just like BEOS by Anonymous Coward · · Score: 3, Interesting

    Meanwhile under the table: Psst...Hitachi... want to sell another Windows box ever again? No BEOS in our BIOS, please.

  27. Well I want Jodie Foster swallowing my 'hood by Anonymous Coward · · Score: 0

    Oh, I guess I can't pay her enough to do that.

    Alright, how about a version of Diablo 3 that doesn't require Steam? Dang, not even that?

    1. Re:Well I want Jodie Foster swallowing my 'hood by Rudeboy777 · · Score: 1

      Ask and ye shall receive! Diablo 3 doesn't require Steam!

      --

      From hell's heart I fstab at /dev/hdc

  28. Might increase the marked for free os desktops? by Youngbull · · Score: 1

    This might raise awareness of the windows tax. The main problem with it is that most buyers intending to use some other operating system will accept the extra cost, install whatever they like over windows and never look back. Microsoft got a good deal going, locking in a machine to use windows and nothing else is unnecessary.

    However, if there is no way to run anything else then windows on a machine, it will make a small but noticeable decrease in sales. Perhaps this will increase the marked for desktop machines with a free os installed, with the possibility of tweaking or disabling secure boot, since "locked in" desktops is not a preferable option for some users.

  29. "in"secure boot by scharkalvin · · Score: 1

    The problem with the secure boot system is that it won't work. It will fail for the same reason that DRM encryption on DVD's and BD disks failed. They were eventually 'cracked'. As soon as a third party OS (Linux, BSD, Mac, etc) is available for installation on systems with secure boot the 'secret' will be out to the malware writers and they will find ways to get in via subterfuge.

    1. Re:"in"secure boot by WorBlux · · Score: 1

      DVD- a fairly week key (something like a 52 bit cipher, with an implementation that brings the effective strength down to 40 bits). VLC will just brute force any dvd's that don't have keys in it's database. Blue ray has not been cracked the same say, any attacks have relied on poorly guarded device keys. (which are continually chased by revocation lists). Practically this will mean there will be some OEM's who have leaked keys and some that don't. HDCP has theoretically been cracked, but nobody has hardware that will do it in real time. But at any rate it's another layer.

    2. Re:"in"secure boot by letsief · · Score: 1

      It's not comparable. As WorBlux said, DVD's encryption scheme was just weak. UEFI secure boot uses much, much stronger cryptography. BluRay uses cryptography of similar strength, but the problem with BluRay is that you had to give every bluray player (hardware and software) a copy of a secret key. There are lots of different players, and it only took one poorly protected key to leak out to destroy the security of that scheme. And to make matters worse, you were basically giving everyone devices that held those secret keys.

      In the case of UEFI secure boot, you don't need to give everyone a secret key. You just need to give them a public key. It doesn't matter if someone can read that public key- you just can't let them [easily] change it.

  30. Apple will profit by Anonymous Coward · · Score: 0

    You can still buy a Mac to run Linux on consumer hardware. Pretty solid and idiotproof hardware at that too (my circa 2006 C2D MacBook running Debian has been dropped to the floor a few times and it still holds together, try that on an Acer or even on a modern soft floppy plastic Lenovo).

    1. Re:Apple will profit by iamacat · · Score: 1

      I am sure Apple be front and center in this effort, probably up to requiring all user-level applications to be signed with their developer keys. I am even sort of sympathetic. My freedom to save $100/year before hacking my own computers is not as compelling as freedom of normal folks not be be p0wned.

    2. Re:Apple will profit by jo_ham · · Score: 1

      Why do you have to pay $100 per year to "hack your own computer"?

      The dev tools on OS X are free, and you can write as much software as you like with them, for free.

      If you want to publish on iOS in the store, *then* you need to pay the $99 fee, but anything other than publishing software to iOS devices (ie, all OS X development) is free if you have OS X.

    3. Re:Apple will profit by iamacat · · Score: 1

      I am just saying I should pay that $99 so that if a regular user gets p0wned, there is at least address/SSN/bank info on file to round up the offender. Certainly there is a potential for abuse by Apple, or by repressive governments, but currently millions of people get abused and placed in financial, personal and sometimes legal jeopardy. We should look for a balanced solution rather than just insisting on outdated status quo.

  31. Microsoft are missing the point... by Anonymous Coward · · Score: 0

    "We believe it is important to support this flexibility to the OEMs and to allow our customers to decide how they want to manage their systems."

    I couldn't give a f**k about Microsofts customers or OEMs. I'm solely interested in my ability to manage my system.

  32. Check out submitter's account by GameboyRMH · · Score: 0

    CSHARP123 is another Microsoft shill. But he's not a front-line guy, rather more of a support guy, submitting pro-MS / anti-competition stories and doing "reputation management" in the firehose.

    http://slashdot.org/~CSHARP123

    --
    "When information is power, privacy is freedom" - Jah-Wren Ryel
  33. Phone OS, same or different? by robbyb20 · · Score: 0

    How is this any different than phones running Android or Symbian? The OS is developed, then phone manufacturers aquire the OS, adapt it to their hardware and then lock it down. If you want to boot something else, you have to hack it. I dont see you up in arms about it, you just deal with it. It was only a matter of time before this started happening with computers too.

    1. Re:Phone OS, same or different? by Hatta · · Score: 1

      Who says I'm not up in arms about it? Lack of software freedom is one of the reasons I don't have a cell phone. Locked down cell phones are just as bad, and bad for the same reasons, as locked down PCs.

      --
      Give me Classic Slashdot or give me death!
  34. The concern is valid, if misplaced by onyxruby · · Score: 3, Insightful

    There is still cause for concern and the concern is misdirected at Microsoft. The bigger cause for concern should be the Motherboard manufacturers. Look at the issue from their perspective. They pre-install a certain number of certificates at the factory (Windows 8...).

    They then have the choice on whether or not they want you to be able to install additional certificates beyond what it came with from the factory. In order to do this they have to enable the feature to allow the certificate store to be updated or the feature to be turned off. They also have to manage additional new certificates and or supporting the user installing their own. That means that they have to provide tech support to allow you to do this. That means additional testing beyond what it comes from the factory, additional support costs for users having trouble and so on.

    Their financial interest is arguably in making sure that the certificates they expect you to need are included and that you have no way to modify this as that costs them money for what they will perceive as a market that isn't worth catering to. There is also the added fact that a motherboard that is locked to a certain Operating System can't run a new Operating System when it comes out. That translates into planned obsolescence where the user /has/ to replace their motherboard when a shiny new OS comes out that they want.

    There is only one thing I can think of that would prevent this issue from being widespread on most motherboards. Enterprise environments need to use tools like Altiris to deploy OS's with PXE boot. If an enterprise can't image their computer they can't use it in fleet deployments and they won't buy it. Of course this does nothing to protect home users that don't have this requirement.

    Bottom line, UEFI is an issue, but not for the reasons that everyone thinks it is.

    1. Re:The concern is valid, if misplaced by Dr_Barnowl · · Score: 1

      UEFI supports PXE ; and if the remote bootloader image is correctly signed, then it will boot, so it's not an issue to produce OS images, as long as you don't change components of the chain of trust (the bootloader, the kernel, drivers, etc).

      Your point about planned obsolescence is well made ; changing the signing keys for each OS release would, in the absence of a way of loading new keys, render a motherboard unable to boot that release in secure mode. Of course, the same applies to all "other operating systems", this one just happens to be Windows 9.

      While it's unlikely that secure mode will be absolutely essential for this release of Windows, you can imagine that some features might depend on it - like certain media features.

    2. Re:The concern is valid, if misplaced by dotancohen · · Score: 1

      Their financial interest is arguably in making sure that the certificates they expect you to need are included and that you have no way to modify this as that costs them money for what they will perceive as a market that isn't worth catering to.

      I'm a Linux user, don't get me wrong. But have you ever stopped to think why we are a market that is not worth catering to? The issue is more than just a race to the bottom.

      --
      It is dangerous to be right when the government is wrong.
    3. Re:The concern is valid, if misplaced by Anonymous Coward · · Score: 0

      First of all, the MB vendor's direct marketing reason is to split the product to Pro and non-Pro version, thus making _the same MB_ in 2 versions for different price - Windows-only and "any OS".

      Second, you _usually_ cannot run new Windows on old MB. The reason is just plain hardware perf requirements. The Windows release cycle is longer then the CPU (and often even CPU socket - LGA775 lived a long time, but so lived XP) and especially RAM cycle (DDR3 has different slots then DDR2 etc). When new Windows will appear, your mobo will be _a generation_ back, and you will need to upgrade CPU+MB+RAM in a combo.

      And yes, MS does not care at all about obsolete hardware. At all (except some rare cases of pressure from Intel who failed to synchronize their chipset production timeline with Vista release). Mainly due to aforementioned reason - hardware develops faster then their OSes.

      Also surely the cert check will be done like: Trusted Root Private to BIOS vendor -> cross-cert given by this vendor to MS's root cert - MS's cert to sign the bootloader.

      EFI does not load other files except the bootloader. So, EFI will have hardships imposing policies to the kernel itself and such.

      So, the enterprise images will be fine until the bootloaders in them will be genuine.

    4. Re:The concern is valid, if misplaced by Anonymous Coward · · Score: 0

      Yes, but Microsoft will set some rules on how the manufacturer will use the OEM and what to implement, and I guess one of the conditions will be to lock down booting options in BIOS and file systems it can run.

  35. The Road ahead by Bill,+Shooter+of+Bul · · Score: 0

    If The majority of OEM's do not allow for a disabling of secure boot we will do two things:

    1) Launch a class action lawsuit against the OEMs and Microsoft.
    2) Ask the EU and the US Justice Department to reopen the anitrust lawsuits.

    The only way for Microsoft to avoid these is to require OEM's to allow users to disable secure boot.

    --
    Well.. maybe. Or Maybe not. But Definitely not sort of.
    1. Re:The Road ahead by iamacat · · Score: 1

      You think Microsoft forcing OEMs to do or not do something is a SOLUTION to their abuse of monopoly? Why don't you take it up with DELL directly? They seem to have listened with preinstalled Linux support.

    2. Re:The Road ahead by bws111 · · Score: 2

      Unless you have some sort of proof that Microsoft forced the OEMs to not allow it to be disabled and did not allow for other OS's to be installed, any such cases would be immediately thrown in the trash where they belong. And no, a bunch of whining and 'what ifs' and 'it could happen' and even 'it happened before' do not count as proof.

    3. Re:The Road ahead by Dr_Barnowl · · Score: 1

      They didn't "force" it to be enabled. They merely require it if you want to put the "Designed for Windows 8" sticker on your PC.

      And let's face it, what manufacturer isn't going to want that sticker? They're all controlled by risk-averse corporate drones who know the value of marketing. They know that people will probably choose the one with the sticker, so they MUST have the sticker themselves.

      Currently you can boot your PC from, for example, a LiveCD, by default in many cases.

      What this will require is that you enter your BIOS, turn off an option that may not be there to turn off [1], and is probably marked with a warning that says "Don't turn this off for security reasons!!!!". Which will put many people off. Linux adoption is a small fraction ; what this will do is whittle down that small fraction a bit more, as people who can't figure it out will just give up and possibly even badmouth Linux as being difficult [2] because they couldn't get it to work.

      [1] Why leave it out? Fewer support calls when someone turns it off by accident. Or maybe someone suggested you might... I wonder who.
      [2] Yes, installing Linux is probably beyond many users. But then, so is installing Windows - the only difference is Windows comes pre-installed for the most part. Having installed both, I can honestly say that installing Linux is now easier and faster than installing Windows ever has been (although it was once atrociously difficult).

    4. Re:The Road ahead by Anonymous Coward · · Score: 0

      Quite easily solved by getting the vendors to include the secure Linux signing certificate along with the MS certificate. Oh, there is no secure Linux certificate? Well, I don't think that is either MS's or the OEM's fault.

    5. Re:The Road ahead by Bill,+Shooter+of+Bul · · Score: 1

      Locking out all future competition by default is not an acceptable solution to anti trust issues.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    6. Re:The Road ahead by Bill,+Shooter+of+Bul · · Score: 1

      Its microsoft, of course they have had internal discussions about this. A simple discovery phase would turn up loads of info. They always have in the past. The point I was raising, was that all of this could be avoided with a modicum of foresight by microsof.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
  36. The PC walled garden is coming by elrous0 · · Score: 1

    Been saying it for a while now. People laugh.

    Just keep laughing.

    --
    SJW: Someone who has run out of real oppression, and has to fake it.
  37. Re:Realistically all the need is a clear boot warn by frinkster · · Score: 1

    If they modified the standard so that the system would give a confirmation popup saying

    "You are about to load an unsigned operating system, do you want to do so? To continue may compromise the security of your system.

    This way people could load Linux if they wanted but the "joe average" would know something is wrong if he was compromised by a boot virus. This would actually be more sensible than preventing other systems, otherwise they will have literally thousands of hackers trying to discover the boot signing keys and publish them online like they did for blue-ray.

    That's great, but how is that Microsoft's problem? Seriously, if people want Linux to boot on this new generation of motherboard/firmware, then people need to do the work to make it happen. It's not Microsoft's job. Find an OEM to help and get to work.

  38. Microsoft Control by Curunir_wolf · · Score: 0

    "Microsoft does not mandate or control the settings on PC firmware that control or enable secured boot from any operating system other than Windows"

    What they mean, here, is that OEMs are welcome to refuse to sign the Microsoft contracts for discounted Windows licenses, and just add that extra cost to their computers, which can then boot other operating systems. Good luck selling any when everybody else is undercutting your prices by $100 or so.

    --
    "Somebody has to do something. It's just incredibly pathetic it has to be us."
    --- Jerry Garcia
  39. Yet Another Translation by Sloppy · · Score: 3, Insightful

    I love the "translation" posts because I hate them all individually -- none of them stress my way of looking at the problem. Here's my translation:

    Microsoft supports OEMs having the flexibility to decide who manages security certificates, because they are our customers, not the users. Fuck the users, why should they have any decision making power in what their computers are allowed to do? We didn't get to be the marketshare leader by leaving decisions to users. Those aren't the people who sign per-processor licensing deals in the millions.

    --
    As copyright owner of this comment, I authorize everyone to defeat any technological measure which limits access to it.
    1. Re:Yet Another Translation by Anonymous Coward · · Score: 0

      I'm not a Microsoft Fan, but thanks to your post I can see their point.
      "fuck the users, why should they have any decision making power in what their computers are allowed to do", you say? Obviously that's because your average user knows shit about computer threats. This clearly affects the minor community of computer competent users. But the great majority are better off with microsoft or OEMs restricting them.

      The averege user still can't restrain from downloading attachments from emails.

    2. Re:Yet Another Translation by Anonymous Coward · · Score: 0

      Corporate users also sign major deals, though, and they need to do things like upgrade their OS and load custom OS deployments, neither of which allow OEMs and, in particular, motherboard makers to do the really dickish things we're all concerned about. They also need to do things like, you know, roll out a big Linux-based data center because they've invested in Linux and that's what their employees know and that's what their in-house tools have all been written for.

      So, worst-case, OEMs sell two grades of system, one for consumers and one for enterprises, and only the consumer-grade stuff is locked down. This is worse than it is now, but it seems to open the door to people buying a bunch of those enterprise systems, maybe pre-loading Linux onto some or all of them, and selling them one-by-one to individual geeks. If that happens I may never step inside a Best Buy ever again.

  40. Re:Realistically all the need is a clear boot warn by Chrisq · · Score: 1

    If they modified the standard so that the system would give a confirmation popup saying

    "You are about to load an unsigned operating system, do you want to do so? To continue may compromise the security of your system.

    This way people could load Linux if they wanted but the "joe average" would know something is wrong if he was compromised by a boot virus. This would actually be more sensible than preventing other systems, otherwise they will have literally thousands of hackers trying to discover the boot signing keys and publish them online like they did for blue-ray.

    That's great, but how is that Microsoft's problem? Seriously, if people want Linux to boot on this new generation of motherboard/firmware, then people need to do the work to make it happen. It's not Microsoft's job. Find an OEM to help and get to work.

    That's a bit like saying that if someone campaigns for a system that would only allow you to use one bank's credit card in all shops the lock in would be nothing to do with them but the shops problem.

  41. Re:Realistically all the need is a clear boot warn by maxwell+demon · · Score: 1

    Just make the option a jumper on the motherboard, and you're virtually guaranteed that only people with at least some clue will change it.

    --
    The Tao of math: The numbers you can count are not the real numbers.
  42. Make it part of the standard by Wattos · · Score: 1

    Why can't you make adding and removing certificates (or disabling the whole system altogether) part of the UEFI standard? That way, any hardware which claims to be UEFI compliant must implement adding and removing certificates. Failure to comply would result in either: high fines, or a free refund for a customer.

    This would solve the issue. Isn't this how HDMI (or was it DP) does it?

    1. Re:Make it part of the standard by bws111 · · Score: 1

      You do realize that there is no law requiring anyone to use UEFI, right? About the most that could happen would be the owner of the UEFI trademark (if any) could sue for trademark infringement. And that is quite easily avoided by manufacturers - just don't call it UEFI.

  43. Mafia ( united states of god ) by Anonymous Coward · · Score: 0

    And ofcourse the ones that secures monopoly of Microsoft will be best treated ...

  44. Move along .. nothing to see by MrMickS · · Score: 2

    How many non-technical home users install a new OS on their hardware? How many of them even bother with an upgrade to a later version of Windows? The percentage has to be so small as to be non-existant. I'm not trolling here, I think its a legitimate question.

    To expand on it. Computers have become commodity devices. People buy one, use it up, buy a new one in the same way they do TVs etc. As long as it lets them do the things they want they don't really care if its got the latest software on. They certainly don't care enough to install a new operating system. Most of them wouldn't even know that this was an option. This is the general population, not the tech elite that read slashdot. So, does this stop people who want to install a different OS from installing it? Yes and no. They might find that its not worth buying systems made by X, but they could always build their own, or buy from a different OEM that provides the access they need.

    TL;DR its not a problem that will affect the vast majority of users. Those that it will affect will have an understandable way around it.

    --
    You may think me a tired, old, cynic. I'd have to disagree about the tired bit.
    1. Re:Move along .. nothing to see by Anonymous Coward · · Score: 0

      How many non-technical home users...

      Way to pigeon hole it down. How many people that can't use a light switch change their light bulbs we should just solder those suckers to the lamps.

    2. Re:Move along .. nothing to see by Anonymous Coward · · Score: 0

      You are making an assumption that a consumer can't become Linux user. I an assure you it does happen. Just look at home many Linux users have Acer - no sane /.er would ever consider buying Acer.

    3. Re:Move along .. nothing to see by roc97007 · · Score: 1

      > To expand on it. Computers have become commodity devices. People buy one, use it up, buy a new one in the same way they do TVs etc.

      Um, maybe. That's certainly in the best interest of manufacturers and is clearly what *they* want us to do. See the beginnings of a push to 4K now that Blu-ray (despite being pointless on sub-42" sets) has a somewhat-firm foothold. However, as to what really happens -- I couldn't verify this through direct experience. I've only owned three TVs since 1985, and one of those was replaced by the manufacturer as the result of a class action lawsuit. (Sony WEGA.) My latest computer was built in an enclosure I originally bought more than 10 years ago. We tend to buy higher end appliances, then keep them for as long as we can, upgrading them as necessary. I'll admit this isn't always the best way to do it -- my current sound system is a rats nest of separate amplifiers and external surround decoders, because that's all there was at the time. I just haven't gotten around to replacing it with one of those do-everything boxes, because the current system still works, sorta.

      I've owned every MicroSoft operating system since Windows 3.1, a fact I'm not entirely proud of, but I'm a geek and it's part of my job. I've also had OS9 and OSX (Power-based) systems, and Red Hat starting with version 5. In no case were they ever attached to an appliance that didn't get upgraded until I replaced the appliance. But I couldn't say what real people do -- it's not like I've taken a poll.

      --
      Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
    4. Re:Move along .. nothing to see by Dr_Barnowl · · Score: 1

      How many non-technical home users install a new OS on their hardware?

      You're right, it's not many. The point is, that even all the UEFI implementations have a setting to disable secure boot, or add signing keys to the keystore, that is puts an obstacle in the way of non-technical users trying Linux out.

      Currently, many systems are configured such that you can boot from a LiveCD by default. People can try it out without any risk.

      If you have to turn off an option that likely has a help option that says "Don't turn this off, for security reasons", people are going to be dissuaded. They're going to be dissuaded just because they have to know that the option even exists. If they don't, what's going to happen?

      Perhaps UEFI will say something like "You inserted a boot media that has an insecure bootloader. It may contain viruses or other malware. Do you really want to boot this?". And this will deter a few more (although not so many, if the number of people installing malware via extra smiley sets for their IM client is any indication..)

      Those of us who see the value of Free Software are a niche market, but currently, we are a niche market who can buy commodity hardware that everyone else buys. Soon we may be a niche market that has to carefully screen our purchases. Manufacturers tend to charge more for niche products (justifiably, because they have fewer economies of scale) which means that some of us will inevitably find themselves priced out of the market, thus reducing adoption.

    5. Re:Move along .. nothing to see by Anonymous Coward · · Score: 0

      If the OEM in question allows UEFI secure boot to be turned off, you have a way around it. If not, recovering from certain terrible types of crashes becomes even more difficult. You did make that recovery CD as soon as you could, right?

    6. Re:Move along .. nothing to see by Anonymous Coward · · Score: 0

      Problem is that those who have tech savvy enough to install another OS might not realize that this is a requirement. Red Hat is likely doing this for two reasons: 1) to warn those of us on places like Slashdot to know to look when buying and 2) to raise alarm prior to Win 8 so that manufacturers think twice.

      Do not think for a second MS is being mostly benevolent here and this isn't something they hoped would be left covered until the launch. Kudos to Red Hat.

    7. Re:Move along .. nothing to see by Anonymous Coward · · Score: 0

      Except when you buy a new laptop with Windows 8 just to find out it is total crap, and your Slashdot reading friend tells, hey, there is this thing called Ubuntu, but guess what? You cannot use it without buying a new laptop.

      Maybe this will only happen to a fraction, but YES it IS a big deal!

    8. Re:Move along .. nothing to see by Anonymous Coward · · Score: 0

      I think the data about personal (typically a graphic desktop used for something other than a server) Linux use is a bit difficult to track down, since nobody is keeping track of sales figures. There are clearly millions of Linux on x86 users in the US alone. Whether it is 1% or 5% of the user base is very hard to pin down.

      This doesn't include users who use devices which come with Linux/Android installed, or embed Linux. Embedded Linux is probably close to 90% of households with on-line access (either in their TV, router, DVR, etc.).

      Sure, most people are brainwashed into thinking there isn't an alternative (ahem). If there was not abuse of monopoly share by Microsoft, vendors would likely be happy to provide alternatives. I spoke to Lenovo reps. just two years ago (after Microsoft had promised to never, never, never again...) who said that they had to stop doing pre-installation of Linux (choice of RedHat or Novell SuSE) because Microsoft said they would jack the price of Windows up if they kept on doing it. They pulled it from their website, and you had to call up and ask for it, but even that stopped.

      Building your own laptop, esp. one with TPM, isn't very practical.

      Buying your own home PC from a Best Buy, rather than assembling it from easy to put together parts you can order from New Egg for much less (and get what you really want), seems like a rather silly notion, but people do it. Now if you wanted to sell a Linux PC in Best Buy, I bet you would run into a lot more resistance, even people liked it better (or could not tell the difference!) from Windows 7 (as was shown two years ago w/ KDE 4.5 v. Win7--I still think KDE is easier to use and looks better).

      Best Buy has allowed Microsoft to fill their "tech sales" people with lots of FUD/downright lies about Linux. I don't think you are going to get a chance, even if you could meet their volume/price requirements. They cannot afford the pain Microsoft would inflict upon them for allowing a competitor loose on the sales floor.

      Just because things are wrong now, doesn't mean that it cannot be better. Microsoft represents a significant threat to people's freedom of choice, and is a very pervasive threat to security, liberty, and privacy. Letting the Tyrant throw another loop of rope around the necks of people isn't a solution to anything.

    9. Re:Move along .. nothing to see by Jimbob+The+Mighty · · Score: 1
      But, how many non-technical users' kids/friends are technical, and want to upgrade or recycle their hardware when it is no longer needed or used for its intended purpose? What might no longer cut it as a high end gaming rig can easily be repurposed into a meda centre, or RAID, or any number of purposes.

      How many non-technical people went 'Vista is shit, I want 7', and their kids chimed in with 'Get the full OEM version + a HDD, don't bother with the retail upgrade'?

      Many 'non-technical' users are able to recognise themselves as such, and defer to people around them for advice.

    10. Re:Move along .. nothing to see by mgiuca · · Score: 1

      But this is exactly why it is a problem. If they were doing something that was going to cause a lot of people to complain, it wouldn't work. Instead, it is very subtle: it is something that most people won't notice, except that it will limit everybody's choices.

      Yes, the geeks among us will be able to either a) buy different hardware, or b) tinker with existing hardware to make it work, but that presents a number of problems:
      * Those of us that want to run an alternative operating system potentially have to pay more for hardware.
      * It could become impossible to switch a Windows 8 machine to a non-Windows-8 machine, instead requiring the purchase of new hardware.
      * For non-technical people, this is a major blockage for switching to an alternative operating system.

      If you think about an OS like GNU/Linux as being "for geeks only" then that last point isn't such a problem. Only, that's wrong. Linux is now at the level that it can be used by non-technical people, and they deserve to benefit from its freedom just as much as geeks. Only now they have new major technical headaches preventing them from switching. They won't complain about this, they simply won't use it. So everybody loses, but nobody complains -- perfect for Microsoft.

      This is exactly what's wrong with monopolies. There tend to be very few complaints because everybody uses the monopoly product. There is not much desire from the user base to switch to something else, because there is nothing else. But the user base would be advantaged if there was an alternative product, so we should not condone measures that prevent the majority of users from accessing an alternative product.

  45. Cell Phone Analogy by PPH · · Score: 1

    This resembles locked vs unlocked cell phone policies. Here in the USA, the gov't kow-towed to network operator's desires and allowed the distribution of locked cell phones. Meanwhile, in many European countries, governments upheld their citizens rights to take their hardware to any network they wanted.

    I think the PC market will work in much the same way. The EU will protect customers and mandate handing the boot keys over to them. The USA will let Microsoft muscle OEMs around and withhold boot options to get the affordable Windows 8 licenses. So Linux users will ship PCs in from the EU.

    US retailers will scream about the loss of business. US Customs will respond by training dogs that can detect unlocked PCs and go through incoming freight.

    --
    Have gnu, will travel.
  46. My laptop has this by PARENA · · Score: 1

    My pretty new Samsung RV520 comes with an option in the BIOS to turn it off. I didn't know about this wonderful "feature" so I was baffled why no single Linux based 'Live CD' or install DVD would boot. Until I found that option. Then it was goodbye to all existing partitions and hello freedom to install what I want.

    --
    Here's the secret to immortality: ...oh dang, I forgot.
  47. This is a UEFI feature, Not a Windows Feature by D-OveRMinD · · Score: 1
    UEFI allows firmware to implement a security policy
    Secure boot is a UEFI protocol not a Windows 8 feature
    UEFI secure boot is part of Windows 8 secured boot architecture
    Windows 8 utilizes secure boot to ensure that the pre-OS environment is secure
    Secure boot doesn’t “lock out” operating system loaders, but is is a policy that allows firmware to validate authenticity of components
    OEMs have the ability to customize their firmware to meet the needs of their customers by customizing the level of certificate and policy management on their platform
    Microsoft does not mandate or control the settings on PC firmware that control or enable secured boot from any operating system other than Windows

    Solution: If you don't want it up to your particular big name vendor, build your own system. You can bet the full UEFI spec will be implemented on Gigabyte, Asus, MSI, and other boards, where you have the choice of disabling the secured boot environment.

    Also, the pre-boot environment in Windows 8 clearly allows the booting of "Other OS."

    1. Re:This is a UEFI feature, Not a Windows Feature by Anonymous Coward · · Score: 0
      It's like saying that the ability to kill people is a knife's feature, not a murderer's feature.

      What you are missing is that Microsoft is once again leveraging its monopolistic prerogatives in the PC market (the logo program) to make installing non-Microsoft operating systems either difficult or impossible. *This* is the problem, not the UEFI feature.

      Oh, and most people can't build laptops yet. I'll bet tablets are even harder to assemble.

  48. Get over it people by Anonymous Coward · · Score: 0

    Much ado about nothing.

    Look, what Microsoft is saying here is they support an OEM's right to decide if they will secure an installation of OS on their hardware products. This is what Apple has been doing for years.

    Microsoft is NOT a hardware vendor, so they do not have the right to decide which OS you run on your PC, and nothing about this suggests Microsoft is going to force you to run Windows for-ever more if you install it on a new PC. The PC industry is made up of many many OEM's and some of them are going to want to lock down their computers to run only Windows.

    So, what does this mean for you? Well, if you buy a Dell computer and Dell decides to lock out installation of Linux, then don't buy Dell, period, end of story. Move along.

    This is not Microsoft saying that if you install Windows 8 on a PC then you can never install any other OS ever again on that box.

    I am tired of the idiot mass Slashaters yelping about stuff they either do not understand or can't see clearly enough to realize this is an incredible NON-ISSUE! These discussions become filled with MS hater *sshats that are so enraged about past experiences with MS that they don't realize how stupid they sound continuing there hatred of MS. A bunch of cavegeeks yelling "Linux good, MS bad" without any context or thought behind the statement.

    Any self respecting Linux fanboy does not buy a Dell computer, they piece together their machine from scratch meaning they are in full of which OS they run. If they happen to install Windows 8, they can freely install Linux at some other time.

    And yes, Microsoft's customers are the OEM's, they are the ones that ship Windows with their computers. Microsoft's market for DIY PC builders is incredibly small, but they are not interested in trying to force that small market to use Windows only.

    So, in translation, 90% of people that buy an OEM PC do not care to use Linux and Microsoft and the OEM's are catering to the desires of this LARGE market, the 10% that do want to use it build their own computers and can install whatever they like on them. This is not an issue!

  49. I can't help but notice by toxickitty · · Score: 1

    A lot of the people commenting here are not really getting the issue, as far as I can tell. The point of worry is control creep, much like the creep that is worried about when they start censoring the "bad things" off the Internet, I'd be all for it if it wasn't so easy to abuse. The problem is in fact, it is easy for the powers that be/status quo to abuse these systems and they have done so before. I've had laptops where I couldn't even switch the SATA mode, there's nothing to stop them making this into the worst possible situation for those who use OSes besides Windows.

  50. What's the fuss? by MarlonTucker · · Score: 1

    Its gonna take less than a week for this to get cracked, so why is everyone so worried. for the 80% of the population who browse facebook and read emails, its probably quite good to have a secure bios that can't (well, I wont say can't, I'll say *less easily*) get rootkitted, if that's a word... for the rest of us, we can just download the latest crack, apply it, and boot whatever we want.

  51. How else could boot hacks be prevented by jader3rd · · Score: 1

    I suspect (I don't know) that the scenario that's trying to be "fixed" is the opening scene of Ghost in the Wires. What happens is Kevin Mitnick gets himself into a building, find the Domain Admin's computer, shut's it down, boots the computer off of a USB key, and install's a key logger onto the system. The computer boots back up, with a key logger now installed, OS security completely bypassed. Is there another solution to this scenario?

    1. Re:How else could boot hacks be prevented by kvezach · · Score: 1

      Yup, the SSH way. If the bootloader changes, pop up a "WARNING: key has changed!" text, with a revert-loader option. If the UEFI is passworded, require the user to input the password if he wants to proceed without reversion. This means that corporate desktops won't be compromised this way (since the end user doesn't have the password and Mitnick doesn't either), and should give other users some reason for concern. If the other users press "go on ahead" anyway, well, there's only so much you can do against a dancing bunnies attack. As another poster pointed out, if users are that gullible, the malware could just as easily do a denial of service attack by asking the user to stick a fork into the nearest outlet.

    2. Re:How else could boot hacks be prevented by jader3rd · · Score: 1

      If I'm hacking in at the BIOS level wouldn't I just modify they key as part of my hack?

    3. Re:How else could boot hacks be prevented by letsief · · Score: 1

      You can probably implement something pretty close to this if you fully implement the UEFI specification. I think you can whitelist hashes of UEFI device drivers and boot loaders, in addition to verifying them using digital signatures. Though, I'm not sure anyone will implement that part of the UEFI specifications.

    4. Re:How else could boot hacks be prevented by kvezach · · Score: 1

      You're not hacking at the BIOS level, you're hacking at the bootloader level. But even if the malware were to try to tinker with the BIOS, that vaunted TPM could just deny it access to that part of the CMOS (or flash or what it is that holds the key/hash). So the UEFI would work like this: in either its own flash or in CMOS, there's a region that stores a hash or set of hashes. The computer comes with the hash for well-known bootloaders and, on boot, checks if the loader hashes to one of them. If not, it checks if it hashes to the user override. If neither, then up goes the warning -- and if the user presses "accept", the new hash gets loaded into the user override field. In any event, after this has been done, the TPM (or UEFI, or whatever is responsible for it) locks access to that part of flash or CMOS so that it can't be attacked from the outside.

  52. You mean 'PERCEIVED' gorilla status by Anonymous Coward · · Score: 0

    Consumers have many OS choices on all shapes and sizes of devices. If microsoft's goal is to gain lock in on the consumer market, and then own the smartphone and tablet market, they are 2 days late, and a Euro short.

    They tried to lock down the very first PC's and failed. The PC only became popular because it was an open platform.

    As for the Canard that the BIOS needs to be updated, I have been hearing this for years. C'mon. All the boot loaders are already written.

    You need secure boot, trusted boot? Install a card, or pay extra for a special motherboard to fix *your* problem. If the problem was that big, somebody would have made such a motherboard and be selling it to you.

    Security Keys in the BIOS? That's a clusterfuck and a brick event waiting to happen. Not in my server room.

    No, I am not flashing or otherwise updating BIOS's. Copy that? Received Transmission? Confirm.

    There are 6 updates for your BIOS. Please install and then reboot your critical server and pray that it comes back up. NO. NO. NO!

    GOT THAT? I AM NOT UPDATING MY BIOS. EVER.

  53. To put it rather crudely... by ArtFart · · Score: 0

    Microsoft is promising not to come in your mouth.

  54. Re:Realistically all the need is a clear boot warn by ceoyoyo · · Score: 1

    Well, if you really wanted to run whatever OS you want, you could always buy a Mac.

    Oh, the irony.

  55. Current EFI implementations... by Alex+Belits · · Score: 1

    ...run on top of PC BIOS.

    If anything, they add more crap to the giant stinking pile of crap that is PC BIOS.

    --
    Contrary to the popular belief, there indeed is no God.
  56. Huh? by apexwm · · Score: 1

    The comment by Microsoft basically says nothing.. it doesn't clear up anything. As usual, Microsoft doesn't play well with others, and essentially users will be left scrambling to find a way to do something because Microsoft doesn't bother. Thanks Microsoft. Thankfully, I stopped using Microsoft software years ago and use Fedora Linux now, so I've got nothing to worry about.

  57. weak protection by Gravis+Zero · · Score: 1

    i mean, if you write over the BIOS then you can effectively wipe out any protection UEFI can provide. please dont tell me that it's protected from flashing unauthorized firmware because we both know those verification systems can be cracked.

    with that much storage capacity, you can make some serious malware.

    --
    Anons need not reply. Questions end with a question mark.
    1. Re:weak protection by letsief · · Score: 1

      You're absolutely right that you can wipe out protections if you can muck with the BIOS. But computer vendors are working on solving that problem too. Did you see this: http://en.community.dell.com/dell-blogs/direct2dell/b/direct2dell/archive/2011/07/22/securing-government-it-from-the-ground-up.aspx ?

  58. My favorite quote by Anonymous Coward · · Score: 0

    My favorite quote:

    For the enthusiast who wants to run older operating systems, the option is there to allow you to make that decision.

    (emphasis mine)

    Way to put a spin on it.

  59. Angry by rtkluttz · · Score: 1

    D@mn. Even their choice of terminology pisses me off.

    "OEMs having the flexibility to decide who manages security certificates and how to allow customers"

    To OEM's and Microsoft, How about once I've paid for the computer you F-off unless the HARDWARE breaks. The OWNER makes the decisions. Period.

    --
    Digital is, by definition, imperfect. Analog is the way to go.
  60. Clarification... by roc97007 · · Score: 1

    > 'Microsoft supports OEMs having the flexibility to decide who manages security certificates and how to allow customers to import and manage those certificates, and manage secured boot. We believe it is important to support this flexibility to the OEMs and to allow our customers to decide how they want to manage their systems.'"

    Yeah, that really clarifies. And Microsoft has never leaned on OEMs to get them to enter into business deal that benefits Microsoft at the expense of competitors. Oh, wait...

    But seriously, Microsoft has never required a customer to pay that portion which is a Windows license when buying a PC even if the customer never intends to run Windows... on... said... machine... oh, wait.

    Yep, that's really clear now.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  61. Re:Realistically all the need is a clear boot warn by Jonner · · Score: 1

    If they modified the standard so that the system would give a confirmation popup saying

    "You are about to load an unsigned operating system, do you want to do so? To continue may compromise the security of your system.

    This way people could load Linux if they wanted but the "joe average" would know something is wrong if he was compromised by a boot virus. This would actually be more sensible than preventing other systems, otherwise they will have literally thousands of hackers trying to discover the boot signing keys and publish them online like they did for blue-ray.

    Unfortunately, the average Joe would just confirm without reading or understanding the warning. Why do you think malware is so widespread today? As long as there's an option to disable secure UEFI in the firmware setup, that's good enough to support other OSes while keeping the average Joe from rendering any benefit from it useless.

  62. Return everything by Anonymous Coward · · Score: 0

    I can probably hear some people yell "boycott". Well... those people are wrong. What you need to do is go buy the UEFI machine, try to install Linux or boot a Live CD (you do have to do this, you can't just look at the box), then return the product for a full refund. Buy another machine with the same problem, repeat. Multiply this by all the Linux users out there (assuming they can be bothered to do this). Watch vendors go ballistic, as the number of open box machines in their stocks grows insanely fast.

  63. UEFI key kit by sgt+scrub · · Score: 1

    The OEM should provide a way that allows the purchaser to program keys into EFI and the OS should allow the installer to notify the OS install process of their key. Personally I prefer there to be no way of making changes to the EFI without physical access. It should be a process of 1) jump pins 2) boot CD 3) program or update. This would place the control in the hands of the owner not an OEM or OS vendor.

    --
    Having to work for a living is the root of all evil.
  64. proxy war tactic by evuraan · · Score: 1

    In short this sounds like a proxy war tactic. MSFT has the "OEMs" lock down future BIOS to boot just Windows OS.

    "Oh you wanna run Linux on your machine..? Too bad your OEM does not allow that...! Instead please keep staring at that shiny Windows sticker on your machine...!

    Profit!

    //FWIW, I and my org will not be buying hardware locked down to a MSFT OS. Get a clue, if you want my $$.

  65. Ghost of Palladium by Anonymous Coward · · Score: 0

    Remember all the uproar from years back about TPM/Palladium? Remember how it was going to eat our (Linux/BSD) babies? And how it didn't show up, and everyone assumed it more or less "went away"... Guess what. It was just hibernating. It's awake now, it's hungry, and your first-born (non-Windows-install) is looking rather pleasantly plump with some BBQ sauce.

    We've grown oh-so-fucking-complacent. And now we reap the harvest we've sown for years.

    I plan on running my out-of-date 890FX-based motherboard for as many years as I can. Grandfathered hardware will become the tinkerer's/hobbist/hacker's chosen platform, because of bullshit like this. Microsoft keeps squeezing the loopholes that allow "foreign" installations tighter, making it harder and harder to get off of Windows; give it about 10 more years, and the memory of "you can install what you want" will finally be "you install what we tell you to, peon."

    Before people say "but no it's always been this way", let's look at a little history:
    - Windows XP, introduces Windows Genuine Advantage, which immediately fails software installs on Wine (because it's not Windows).
    - Windows Vista, introduces "secure audio path" and other core DRM elements, but isn't heavily pushed (yet) because of driver grief. The community buys some valuable time.
    - Windows 7 aka Vista Second Edition (remember 98/98SE?) retains all the DRM elements, and starts to finally push things forward. We pretty much pissed the time away that we got with Vista, with Ubuntu being the only viable contender to emerge from 5 years of stagnation.
    - Windows 8, introduces "secure boot", which really means "securely booting our revenue stream until your computer is dead".

    What comes next? I can only guess:
    - Windows 9, we will tie the license to facial recognition software so that you can never transfer it to another user when you sell the computer. The facial recognition is part of the new "secure logon".
    - Windows 10, you will rent the software "by the year" as part of Azure 2. Failure to pay = failure to access your data. If you don't pay up soon...your data gets deleted after just 1 year. Goodbye family photos, home finances, and other important home use items...
    - Windows 10, we start our original goal that Bill G. wanted, namely, to be the middleman in your transactions. We get a cut.

  66. Why are you blaming MS? by Anonymous Coward · · Score: 0

    It's OEM's commercial interest, not MS's.

    For now, the ability of installing Ubuntu on laptop seems to be "free as air". But sorry, this can change. In mobile world, for instance, it is not free, and requires excessive hacking.

    There is no freedom to run Linux on iPhone, unless you will hack it (and they become more and more resistable to hacks, for instance, iPhone 4's baseband _cannot be operator-unlocked for a year_ without this ugly Gevey SIM hardware hack which bastardizes the whole GSM protocol and can cause blacklisting of your account by the network operator).

    So, why do you think OEMs will not go the Apple's way and, for instance, sell the Windows-only restricted laptop for cheap, and _the same laptop_ but not restricted for Windows - for more money? for me, this is logical. Same as with cellphones - operator-unlocked phone is more expensive than the locked one.

    The OEMs will even market the unrestricted version as "Pro", and "Geek's Friend", as "Install the True Real OS of Linux for this small additional money" and such.

    The thing is that 99% of laptop users do not care about Linux, so saving money on this non-Pro version can be important for them.

    As for MS, they a) do not ship the assembled systems, laptops, motherboards and BIOSes b) do not write EFI firmware c) have only partical control over it, since EFI is Intel's thing c) they do not care. The percentage of desktop/laptop Linux users is insignificant and has no serious growth since around 2004.

  67. Real Reason This Has Come To Pass by macromorgan · · Score: 1

    I'm betting it's because Microsoft's WGA or WAT or whatever they're calling their activation process is currently bypassed for OEMs by way of a BIOS certificate, and the stuff necessary to bypass it by the warez scene is typically a bootloader. I'm betting that the only way companies get to use the OEM way of activating Windows with a single key is if secure boot is enabled. The impact to malware and Linux are both probably incidential benefits to Microsoft. How to tell if I'm right? See if it asks you to activate your copy of Windows when you disable secure boot on your Windows 8 Dell.

  68. This just sucks by Anonymous Coward · · Score: 0

    i'm gonna have to start building my own PCs again...

  69. depends ... by Anonymous Coward · · Score: 0

    The home user that buys motherboards is precisely the kind of user who cares about the ability to upgrade or replace operating systems.

    If I buy a motherboard from newegg that won't let me install Linux, it's useless to me and will be returned for refund immediately.

    The person who buys complete "name brand" computer systems is probably screwed, though.

  70. Trust. by Anonymous Coward · · Score: 0

    Nobody should trust MS unless they have an option not to trust them. I will manage my own keys, thank you.

  71. what concerns me by Anonymous Coward · · Score: 0

    if they do lock it down so you cant change the system and crackers find a way to virus that anyway (which they will no doubt on that one its just a matter of time) will that prevent someone from reinstalling windows if they dont have the origional oem recovery disks made? if they lock it down forceing people to use a specific system will it stop them from repairing the current system when it finaly buckles over?

  72. UEFI could backfire everyone by fsoft · · Score: 1

    Actually, I think this new UEFI Secure Boot could backfire everyone: the user who cannot install a different Operating System; Microsoft could have the same problem when the user wants to switch to another version of Windows; mainboard manufacturers if they have to provide a *simple* way of updating / managing certificates: and by *simple* I mean a very fool proof user interface, not the usual 80-chars-navigate-using-strange-keys BIOS interface they still produce.
    I don't think that UEFI is a feature worth the cost.

  73. Microsoft: Microsoft innocent by Anonymous Coward · · Score: 0

    How interesting. Like a mobster trying to convince the cops that the other guy just happened to run into his bullets... "None of my doings, Sir! I'd never do anything like that!"

    The CAPTCHA for this post was fittingly 'silliest'.

  74. Palladium strikes again! by Antique+Geekmeister · · Score: 1

    None of this is new. The clear desire to control the ability to access hardware, storage media, to boot an OS, andn to authorized applications to run or access to data, was buiilt into the "Palladium" project and was renamed "Trusted Computing". While much of its glamour has been lost, and the difficulty of enforcing its controls has been shown to be hackable with virtualization, it emains a technology designed to prevent access to hardware and data based on commercial licenses, rather than any security or defense of user data.

    This is another attempt at the same goals, to foster and enforce Microsoft monopolies by controlling the ability to use the hardware, itself.

  75. Remote Attestation by Chris6502 · · Score: 1

    I can't believe how little protest the remote attestation aspect has generated. From TFA: "To prove a client is healthy, the anti-malware software can quote TPM measurements to a remote verifier."

    How long before that becomes "The XYZ software can attest that only trusted software components are running." Big content are going to love this capability.

    --
    UNIX: 'cuz you can tattoo it on your knuckles!
  76. Re:Realistically all the need is a clear boot warn by Bengie · · Score: 1

    Or for half the price, build you own computer that supports secure booting Linux.

  77. Re:Realistically all the need is a clear boot warn by ceoyoyo · · Score: 1

    I think the worry is that the motherboard manufacturers will get onboard the Microsoft train. If the paranoia pans out then you might have a little difficulty doing that.

    Unless you enjoy etching PCBs, that is.

  78. why is this a problem? by crutchy · · Score: 1

    if you want a linux box, build one from basic parts and don't be lazy (building is cheaper if you know where to buy the parts)

    if you want a linux box but don't know how to build one, now's a good time to learn

    if you want a laptop for linux, there's ebay

    if you're lazy, don't know what linux is, or just like playing freecell and obsessing over comments on facebook, then you're probably not even aware of any of this and won't be affected anyway

  79. There go dual boots, Here comes DRM by Anonymous Coward · · Score: 0

    No mention of dual booting, if only 1 of the OS's has a signed key. What will you do when you have go go into the bios and disable key checking to run one os and then go back in to enable key checking to run the other bios?

    How many dual booters--if they had to choose, if it were difficult to choose otherwise--would just choose to give up Windows entirely?
    Probably not many...some of use still keep a Windows box around to run a certain application that is vital to what we do.

      The underlying reason for an OS before the OS is not user protection, it is digital content protection, with Microsoft (or the oem's, moot point) loading keys for digital rights protection from software vendors to keep you from:
    installing other OS's
    Installing software like competitors to MS Office, who didn't pay for a key.
    playing music that is not "keyed"
    playing movies that are not "keyed" to you (or to your region).

    stage 1 involves building a wall/hurdle that other os's must bear the cost of.
    stage 2 involves having software companies apply for and pay for a key for their software to run under Windows 8.
    stage 3 involves the music and movie industries applying for and paying for keys to let their products be protected by keys.