 El Quintron... a faint odor of kerosenePremium join:2008-04-28 Etobicoke, ON kudos:2 Reviews:
·TekSavvy DSL
·voip.ms
·WIND Mobile
·TekSavvy Cable
| reply to FF4me
Re: Windows 8 Secure Boot Would 'Exclude' Linux Like others have said here, I'm all fine and dandy with building my own Desktop machine but I doubt I'd want to spend the time and effort to "build" my own laptop, so something has to be done so that another OS can be installed on these new machines.
Assuming MS doesn't cooperate, I can predict a few scenarios:
-Win 7 pulls a Windows XP and ends up living 10 years beyond its planned expiry date.
-Hardware manufacturers start releasing "L" series boards where Windows isn't intended to be installed.
-A workaround is discovered within six months, and MS starts another patent litigation against a hardware manufacturer that won't close the loophole.
I don't think this is the end, but it would certainly be an annoying hurdle to deal with. -- I'm watching District 9 again, and I've come to realize something: Wikus's got it all wrong. If I were morphing into a 9 foot tall hyper-dextrous alien that can shoot lightning bolts and get high off cat food why would I ever want to become human again? |
|
 grunze510 join:2009-02-14 Cote Saint-Luc, QC kudos:1 | Let's say the OEM uses a generic motherboard and flashes their own BIOS on it, wouldn't it be possible to flash it with the generic one which would allow you to disable secure boot? |
|
|
|
 | reply to FF4me Google's CR-48 has the same secure/verified boot feature. Easy to bypass by flashing a new ROM. |
|
 El Quintron... a faint odor of kerosenePremium join:2008-04-28 Etobicoke, ON kudos:2 Reviews:
·TekSavvy DSL
·voip.ms
·WIND Mobile
·TekSavvy Cable
| reply to grunze510 Sure, but then you have to choose between Win 8 or Linux because this process as currently proposed would exclude Linux, or you couldn't have Win 8 if you disabled the "secure" boot.
It's not very cool if you do most of your stuff on Linux and boot into Windows for work or gaming. -- I'm watching District 9 again, and I've come to realize something: Wikus's got it all wrong. If I were morphing into a 9 foot tall hyper-dextrous alien that can shoot lightning bolts and get high off cat food why would I ever want to become human again? |
|
 | My biggest issue lies in laptops. It's not like we have a large affordable market for building our own or I would have been doing it for a while now. |
|
 maartenaElmoPremium join:2002-05-10 Orange, CA kudos:1 | reply to FF4me Too much panic guys.
This "feature" is not going to prevent linux users from buying a laptop. I think we are overreacting here. -- "I reject your reality and substitute my own!" |
|
 wmcbrine213 251 145 96 join:2002-12-30 Laurel, MD | reply to FF4me I'm seeing more Macs in my future... at least they run Unix...  -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 |
|
 MaxoYour tax dollars at work.Premium,VIP join:2002-11-04 Tallahassee, FL | reply to disturbed1 The CR-48 was made to make it easy to turn this feature off with a hardware switch. |
|
 | That gets you to dev mode. Then the CR-48 warns you that OS verification is turned off. But it still has the verified boot.
You need to use flashrom to re-flash the CR-48 with a different rom image than that provided by Google. This gives it an Insyde UEFI bios and allows you to do what you want with the laptop. 
Should a person purchase a proclaimed locked UEFI Windows 8 PC, they would only need to re-flash the rom image -- if/when this rom image is developed. |
|
 | reply to FF4me From The H:
Referring to a presentation (PowerPoint .pptx file) at the Build developer conference, Garrett said that all client systems desktop PCs, notebooks, tablets with a Windows 8 logo must support UEFI Secure Boot and have this feature enabled. However, the way it is described in this document, the second condition at least isn't necessarily mandatory: it could also be that the function must explicitly be enabled by the computer's owner or administrator. Also, as has so far been the case, most systems with UEFI will probably be able to load an optional Compatibility Support Module (CSM) that allows operating systems to be booted in BIOS mode. This is a prerequisite for installing 32-bit versions of Windows because only the x64 versions of Windows since Vista can be installed in UEFI mode. Microsoft refers to systems that can boot either in UEFI or in BIOS mode as "Class 2" systems; systems without CSM are referred to as "Class 3".
However, the situations that will allow multiple operating systems, where some start in UEFI mode while others start in BIOS mode, to be installed on the same hard disk remain unclear this will probably make it difficult to install dual-boot systems on notebooks, tablets and other devices that only have one mass storage device. There may be no choice in some circumstances; the Windows 8 mobile computers with ARM SoCs that have been announced will only ever be available as Class 3 devices. On these devices, however, Microsoft plans to increase platform security by allowing only apps from the app store that have been checked and signed to be installed on the Metro user interface.
Another problem when booting alternative operating systems could arise from hard disks that are fully encrypted with TCG Opal or BitLocker, if the boot loader is required to include functions that allow a key to be submitted to a Self-Encrypting Drive (SED). |
|
 | reply to markofmayhem said by markofmayhem: - The word "required" is used LOOSELY across the sites... "SUPPORTS" is the official term used by Microsoft outside of marketing blitzes. Windows 8 logo certification was the very specific topic of "Secure Boot" when combined with "required", not "will only boot on".
SUPPORTS and REQUIRED are the SAME THING in mslobber speak.
said by markofmayhem: - Mobo manufacturers will sell consumer-retail pieces in "Setup" mode or they won't be able to sell their goods to the public at all: Add your own PK keys! Mobo manufacturers will not abandon their most profitable groups whom use "not Windows 8" OS's: hardware jumper, UEFI user setting, and/or "I'm secure I swear" spoofing in
Who IS the CUSTOMER to Asus, etc.? Just like Broadcom could care less about selling me 30-40 chips, they DO CARE about about selling 300-400,000 to some OEM making some widget..... Same with the OEM MB makers the persons building their own boxes are NOT their customer, OEM builders are.
said by markofmayhem: Is it possible that one day an OEM PC could be purchased that is locked to one version (and COPY) of an OS? YES!
You can PLAN on it and BET on it! Sooner rather than later.
said by markofmayhem: Is it probable? Sorta.... the details lean to no, but this is certainly not something to sit back and "hope". Getting a Linux kernel and bootloader up to speed to support "Secure Boot" should be happening.
Exactly GO NUCLEAR ON THEM NOW, and cut it off before it gets any traction any where, MB OEM's and box OEM's like dell etc.. Tons of boxes purchased from dell etc.. that may come with an infection, but are inoculated by IT to clear it of that disease. Won't be possible with this. |
|
 | reply to maartena said by maartena: Too much panic guys.
This "feature" is not going to prevent linux users from buying a laptop. I think we are overreacting here.
No I don't think there is ENOUGH REACTION, this is a clear cut threat to Linux, UNIX, BSD, and anything else out there now, past, present or future.
A failure to REACT NOW while its still killable v. when its in hardware and its not going away, is TOO LATE.
Go NUCLEAR now! |
|
 markofmayhemI can haz competition?Premium join:2004-04-08 Pittsburgh, PA kudos:4 | said by TuxRaiderPen :Who IS the CUSTOMER to Asus, etc.? Just like Broadcom could care less about selling me 30-40 chips, they DO CARE about about selling 300-400,000 to some OEM making some widget..... Same with the OEM MB makers the persons building their own boxes are NOT their customer, OEM builders are. The "customer" to Asustek is you and I as well as large corporations, governments, non-profit organizations, and others who purchase retail consumer goods. The "customer base" of Asustek will not take kindly to "Windows 8 Only".
said by Pegatron Financial Statement :Pegatron Corporation was established on June 27, 2007. In order to enhance competitiveness and boost productivity, the Company resolved to accept the OEM business from ASUSTeck Computer Inc. on January 1, 2008 to restructure the Company's business. ASUSALPHA Computer Inc. was merged with the Company on April 1, 2008. source
Compal, Quanta, Uniwill, and Foxconn are the OEM big boys... not MSI, Asus, Gigabyte, ECS; they buy many of their components from the others (although Asus and MSI are manufacturers, they do not manufacture the whole).
said by TuxRaiderPen :Exactly GO NUCLEAR ON THEM NOW, and cut it off before it gets any traction any where, MB OEM's and box OEM's like dell etc.. Tons of boxes purchased from dell etc.. that may come with an infection, but are inoculated by IT to clear it of that disease. Won't be possible with this What isn't "possible", exactly?
FACT: Windows 8 will install on BIOS Motherboards, including UEFI boards with "BIOS" modes (I have one, it works great) FACT: Known UEFI images with "Bios" modes can be intertwined with future images to enable the option IF NEEDED FACT: UEFI specifications, shell, and methods to enter "setup" mode are publicly available (requires physical access to hardware) FACT: The one and ONLY computer in existence with Secure Boot was a development tablet manufactured by Samsung with developer-grade UEFI 2.3.1 BIOS by AMI featured for the first time at the Microsoft BUILD conference and had a setting to DISABLE Secure Boot FACT: Secure Boot DOES add security. The only reason "lack of choice" exists is due to the inept approach from others. Apple and Microsoft will be going forward with higher security than Linux YET AGAIN. "Nuke" whom? The kernel developers? Or the companies actually progressing security features ON OPEN SOURCED SPECIFICATIONS! FACT: Windows 8 will allow a touch-screen UEFI shell to boot into NON SECURE BOOT Windows 7, which means Linux CAN be chained. source
Security on Linux has been in a consistent and steady decline for many years, resting on known good times and lack of high-profile vulnerabilities does not indicate the level of secured ability. A multi-partnered, open-sourced, international specifications body has released a methodology to increase security. You will not find a single authoritative source arguing, accurately, that UEFI's "Secure Boot" is "evil", "bad", or "over reaching". This should be viewed as a call to action for development to allow Linux to support the new generation of hardware. We have PLENTY of notice before this issue is real.
An author that isn't a tin-foil-hat-wearing-bunker-dweller had this to write: »arstechnica.com/business/news/20···aign=rss -- Show off that hardware: join Team Discovery and Team Helix |
|
 davePremium,MVM join:2000-05-04 not in ohio kudos:7 Reviews:
·Verizon FiOS
·Verizon Online DSL
| reply to grunze510 said by grunze510:Let's say the OEM uses a generic motherboard and flashes their own BIOS on it, wouldn't it be possible to flash it with the generic one which would allow you to disable secure boot? Not if they're smart enough to enforce the obvious restriction that the 'standlone bios reflash' code cannot be booted unless signed. |
|
 markofmayhemI can haz competition?Premium join:2004-04-08 Pittsburgh, PA kudos:4 | said by dave:said by grunze510:Let's say the OEM uses a generic motherboard and flashes their own BIOS on it, wouldn't it be possible to flash it with the generic one which would allow you to disable secure boot? Not if they're smart enough to enforce the obvious restriction that the 'standlone bios reflash' code cannot be booted unless signed. There's ways around that one as well. The UEFI 2.3.1 specifications include a "setup" mode to add, remove, and restore the PK(s). Finding the combo to get the "BIOS" into setup mode may prove to be more difficult than average patience levels, but once found...  -- Show off that hardware: join Team Discovery and Team Helix |
|
 MashikiBalking The Enemy's Plans join:2002-02-04 Woodstock, ON | reply to FF4me I'll give it 3 weeks before it's broken, especially since MS said that the new Windows activation wouldn't be very difficult to beat. I think that took all of 6 hours for someone. |
|
 | reply to FF4me
MS Denies Secure Boot Will Exclude Linux Lock-out security tech can be disabled, if OEMs want to
Microsoft has hit back at concerns that secure boot technology in UEFI firmware could lock out Linux from Windows 8 PCs, saying that consumers will be free to run whatever they want on their PCs.
In a blog post on Thursday, Microsoft attempted to address these concerns arguing that "complete control over the PC continues to be available" to consumers.
Secure boot is a UEFI protocol, rather than a specific Windows 8 feature, and "Microsoft does not mandate or control the settings on PC firmware that control or enable secured boot from any operating system other than Windows," Microsoft's Tony Mangefeste explains.
"Secure boot doesnt 'lock out' operating system loaders, but it 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," he adds.
Mangefeste cites the example of a prototype Samsung tablet with firmware designed to allow customers to disable secure boot, an option that is open to OEMs.
Just how many OEMs will take this approach remains unclear. Microsoft has effectively batted the question over to its hardware partners and firmware suppliers. What both Microsoft and critics of UEFI seemingly agree on is that unless secure boot can be disabled then Linux can't be run on Windows 8 PCs.
We asked the UEFI Forum to comment on the issue earlier this week but are yet to hear back from the industry group, which promotes and manages the UEFI standard. Members of the UEFI forum include Apple, IBM and BIOS giant Phoenix Technologies as well as Microsoft. |
|
 nwrickertsand groperPremium,MVM join:2004-09-04 Geneva, IL kudos:7 Reviews:
·AT&T U-Verse
| reply to FF4me
Re: Windows 8 Secure Boot Would 'Exclude' Linux After reading this thread, and similar threads elsewhere, I have decided not to panic. I'll sit back and see what develops.
The current boot system for PCs was designed in the early 1980s, when the 10M hard drive on an IBM PC-XP was so large that nobody would ever fill it. Sure, it has been modified to accommodate larger disks, but it is still the same basic system.
If this change is a major redo, then that could be a plus. I expect that the linux world will adapt to it.
As for the certificate to verify the signature on the boot code - what makes most sense is that there be a provision to install certificates in flash ROM. If only Microsoft certs were allowed, there would be anti-trust law suits against MS. Installable certs makes the most sense for flexibility for end users. -- AT&T Uverse; Zyxel NBG334W router (behind the 2wire gateway); openSuSE 11.4; firefox 6.0.2 |
|
 davePremium,MVM join:2000-05-04 not in ohio kudos:7 Reviews:
·Verizon FiOS
·Verizon Online DSL
| reply to FF4me
Re: MS Denies Secure Boot Will Exclude Linux said by el reg :Microsoft has hit back ... Ah, a lovely gutter-journalism turn of phrase. Any statement of disagreement, however expressed, is 'hitting back'.
(Still, The Register does present itself as a red-top ...) |
|
 markofmayhemI can haz competition?Premium join:2004-04-08 Pittsburgh, PA kudos:4 | reply to nwrickert
Re: Windows 8 Secure Boot Would 'Exclude' Linux said by nwrickert:As for the certificate to verify the signature on the boot code - what makes most sense is that there be a provision to install certificates in flash ROM. If only Microsoft certs were allowed, there would be anti-trust law suits against MS. Installable certs makes the most sense for flexibility for end users. This is the concern, but not because "Microsoft holds the only key". Good read on how Windows 8 implements this here: »blogs.msdn.com/b/b8/archive/2011···efi.aspx
Anyone can have a "key". A key, through OpenPGP for example, is nothing more than hash string. What "keyring" that key is associated with is very important. For example, I have 3-4 of the buggers over on Canonical's Launchpad (steps to get your own here).
UEFI uses the public portion of the keys, the same portion of the key I upload to the keyring. UEFI has "Platform Keys (PK)" and "Key Exchange Keys (KEK)". The PK is what is the primary issue... WHICH PK will the OEM's place in their products? Will Dell, HP, Acer, Lenovo, etc. put their own key or will they put Microsoft's as the "Platform Key"? The PK is the one used to add/subtract KEK's. Will Canonical have a "Platform Key" or will it submit to a KEK allowable by Dell, HP, etc's Platform Key? Can Linux.org strongarm Microsoft to be an allowable KEK to their PK? It comes down to, not necessarily the owner of the key, but the owner of the keyring. Would MS's keyring allow Canonical's keys? Would Dell?
This is the "hard" method, getting Linux into the OEM/Microsoft keyrings. The "moderately difficult" method will be to place the UEFI into "setup mode", where PK's can be added and removed. At that time, the end user can place their own PK (if needed) with allowable KEK's they wish to operate under. There seems to not be any other feasible way to ship non-OS installed hardware other than in "setup mode" (the Asus motherboards on NewEgg, for example). The "easy" method is to shut off secure boot. -- Show off that hardware: join Team Discovery and Team Helix |
|