Phoenix's BIOS Roadmap
An anonymous reader writes "Phoenix Technologies Ltd. unveiled a vision and roadmap for a next generation of system BIOS firmware that the company calls "core system software" today, at its Strategy 2004 conference. As defined by Phoenix, CSS is a new category of core system firmware that transcends the boundaries of traditional BIOSes and to deliver "extensible firmware that provides the critical foundation of trust, manageability, and connectivity required for networked computing," in a broad range of devices including desktop and laptop PCs, servers, and handhelds gadgets. Specific technologies that Phoenix is integrating into its d-NA CSS firmware include: support for the Trusted Computing Group (TCG) specification, remote diagnostics and error-checking, intelligent configuration checking and integrated system policy management, automated provisioning of servers and server virtualization, "radically enhanced" device power management, embedded TCP/IP, remote management functions including dynamic provisioning, load balancing and software resource control, and an XML and SOAP standards-based interface to CSS functions."
Trust -- [...] In addition, Phoenix d-NA will incorporate a new class of Windows-advantaged components that leverage the Microsoft CryptoAPI (CAPI) to provide unprecedented trust and intrinsic security for systems running Windows and
If this crap cannot be disabled then I guess I won't be using Phoenix BIOSes in the future. This whole "trust" nonsense is a thinly veiled attempt at shifting some of the security-onus from the OS to the hardware with the blessing of Microsoft along with the side "benefit" of Digital Rights Management.
This may start a whole new style of hacking; releasing BIOSes for flashing which have the DRM/Trust shite removed.
Trolling is a art,
Maybe it's time to start helping out/using LinuxBIOS. I went to SCALE over the weekend and saw a interesting presentaion on LinuxBIOS, it has lots of benifits over other commercial BIOS's.
This is braindead. Introducing a huge layer of complexity between the OS and hardware etc. Really the job of the BIOS should be to do as little as necessary and then hand things off to the OS. Does a BIOS truly need a TCP/IP stack? Perhaps it is time to put a bit more effort in to linuxBIOS.
If I had no sense of humor, I would long ago have committed suicide. -Ghandi
Most of the viruses lately have been of the email-you-are-dumb variety. I'd been wondering where all the excellent boot sector and hardware level viruses of the 1980s and early 1990s had gotten to.
I couldn't stand yet-another I-love-you clone. I want some real destruction!
I want a kitchen sink included in the BIOS!!!
Really... why not scrap all that and add a JVM instead... That at least would be usefull...
Seeing that take a slashdotting is what we're really interested in... totally in the spirit of slash (TM)
Conversion Rate Optimisation French / English consultant
The hardware architecture of the PC IS the open architecture as apposed to Apple, etc. One could argue that MS uses the software to reclose the architecture, but the PCs near ubiquitous nature is due to its open architecture. MS bet on the open hardware architecture and won big.
What value is the manageability component if there's no supervisory CPU (a'la something like a PC Weasel ) so you can actually get to the management interface when your OS is hung in a bad way. Real computers have always had supervisory CPU's. I don't see why the PC world refuses to get it right.
Crypto API is designed to give your applications a consistent and secure way to encrypt data by asymetric encryption. Support in hardware is designed to speed this process up.
It might be used instead of PGP to encrypt your home directory, you can use it to securely communicate over networks, you can use it to generate great passwords.
That it's there is a good thing (tm), but someone might use it to keep stuff from you.
"Welcome to the real world".
Intel has been working on EFI since 1998. This is just a rip off of that.
How do I know that they won't resurrect this:
http://www.cexx.org/phoenix.htm
and then hide it behind the hardware protection scheme to keep me from finding/disabling it?
Phuck you, Pheonix. You have already demonstrated how trustworthy you are!
With the number of features and calls that they are adding, their BIOS is getting close to being an operating system. Frankly, I see this as a good thing for Open Source.
The BIOS does not need to be "open" in order for Open Source to take advantage of this. By necessity they will have to publish their calls and protocols to allow the BIOS to be as effective as it can be. Using this information, Opne Source projects can have direct access to this "mini-os" and be able to build whatever they please around it.
Will this spell the end for Windows? I doubt it. But it may help level the playing field a bit.
Microsoft should (IMHO) take over the bios market. Now, before you go and flame me I should tell you that I have no love of MS (Mac fan here - o the shame of it all). But the one thing that I love about Apple is that they take change and make changes to the hardware to insure the BIOS (we call it "Open Firmware" is up to date and actually functional, unlike PCs. You have no true leader, only many highly influential players all struggling to defeat each other with competing "standards" (and I use that term loosely). I have very little respect for a computer that can not network at the BIOS level or manage anything other than a 20 meg (I forget the real number) hard drive or a floppy with out resulting to extensions (hacks). Your BIOS needs to be trashed and updated and who better than the industry leader. You don't want small insignificant players mucking around with this layer of code, it can only serve to fragment an already hopelessly fragmented market. If they can come out with an open product like Apple's Open Firmware than good for them (so long as they don't prevent anyone from installing a real os).
Remember kids, having an industry leader does not always mean tyranny. Sometimes having an industry leader simply means less anarchy. Hopefully you have a chance for a decent solution. So be careful of assuming that MS "leading" the industry in a particular direction is bad. You PC people desperately need a new BIOS and someone has to write it and get everyone to agree.
But as a side note: if you insist on buying PC's with all their problems, why do you get complain when you end up with an Piece of Crap. If you want true freedom from MS, buy SG, Sun, Apple, or anything else that does not run windows (or not designed in 1980) otherwise you are nothing more than a hopelessly entrapped user. I don't want to start a flame, I just don't understand why any would willfully buy a computer which has advanced very little since it was originally designed and I see BIOS as a prime example of outdated technology that PC people just can't seem to overcome like users of other vendors have.
Which is precisely the problem: if Microsoft has their way, this won't be an option.
The reason why Microsoft wants this so badly is because this would enable Microsoft to charge annual or quarterly subscription fees for their OS. If the PC can't run any other OS, then the PC owner must pay whatever Microsoft demands.
I just bought a Toshiba laptop with Windows XP. The system is horrible; Explorer crashes constantly, networking works only occasionally, and it's already been infected by the MSBlaster virus. The DRM "features" mean that even though I've got a DVD player, I can't take screenshots. And the best part? It can't read CD-R's burned on other machines(DRM???).
Fortunately, I was able to install RedHat 9, and now I've got a functional system again.
However, this might not legally be an option in the future. Consider for example the Lexmark case: Lexmark sued Static control because Static control had to copy the Lexmark handshake code in order to get their cartridges to work with Lexmark printers. Now imagine that instead of printers, it's a PC, and the BIOS requires a digital handshake before it loads an OS. Microsoft of course could pay royalties to the BIOS companies for the copyrighted handshake code. Linux, OTOH, could not. In order to distribute Linux, one would have to distribute the copyrighted handshake sequence; the threat of DMCA action would prevent Linux from even being distributed. (Even if FSS/OS proponents could win the court case, the BIOS companies could enjoin the distribution of Linux until after the case was resolved, effectively killing it.) If Linus found a way around doing the secure handshake, his kernel would be illegal as a circumvention device - in which case, he could be prosecuted criminally by the government.
And Microsoft would gladly pay the small royalty, because doing so would mean that the consumer could not legally install an OS other than theirs. And considering Microsoft's abuse of power in the past, does anyone really think that they won't charge rent for their OS's? The availability of alternate OS's has prevented this in the past, but with this gone, they will be free to charge as much as they want in annual royalties.
If this "Trusted Computing" initiative ever becomes a BIOS standard, private ownership of PC's will be a thing of the past - yes, you paid for the hardware, but you can't legally turn on the machine without a lease from Microsoft.
The society for a thought-free internet welcomes you.
Phoenix has mad several attempts to invade the privacy of PC end-users.
See
Phoenix Phone Home. 2001-06-19
and
Phoenix to embed bootup ads in BIOS
on Slashdot.
Phoenix, with its subsidary Award, is the largest player in the BIOS market. The only other big player is AMI.