Slashdot Mirror
Phoenix Bios to Incorporate DRM
defishguy writes "Extreme Tech is reporting that Phoenix Technologies is shopping a DRM-capable BIOS to OEMS. Reportedly the BIOS with DRM enabled allows for software to be tracked and traced from one PC to another." See also this older story about AMI.
Don't do it, you're pretty easy to replace.
Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
I found their email address, contact them and tell them how much this sucks.
investor_relations@phoenix.com
Yes, of course, we'll just boycott one of the two BIOS makers out there! Phoenix bought the Award makers a long time ago, remember? And the other BIOS builder...is AMI. They also make DRM-enabled BIOSes.
At this point, I can't think of a worthwhile motherboard maker out there that doesn't use the Phoenix Award BIOS. Essentially, it's up to the OEMs, at least...for now.
The best opposition to this would be and Open Source BIOS. I've no idea if this is possible, likely, or already being done. It simply seems like the best response to DRM enabled BIOS.
The OpenBios project has been in the works for a while now.
Time is what keeps everything from happening all at once.
1) Are there any?
No idea, a check around the net may come up with something. However they are specific to the board you are using...
2) How much bios code is reusable between completely different motherboards?
This again depends, on similar hardware, memory controllers, etc...
3) Will we always need a bios?
Well the other option is a ROM monitor or ipl (Initial program loader), those need to be written for the board you have, which is not trivial, esp without the hardware manual (specs, etc.)
E.
Never rub another man's rhubarb - The Joker
DRM works on the basis a unique ID in the BIOS and a central DRM server. You're always the client in this setup. If the application can't connect to the DRM server, you can't use it, although they make give you a few hours "grace" period. It's not the software on the CD but the activity of linking your license with the BIOS UID in the DRM server that makes it stick.
Good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws-Plato
BTW, I do agree, there are other manufacturers out there. Take your dollars somewhere else...
: The New American Corporate Soviet
Loss of Control and Backdoors
Read Microsoft Aims for Protection--From Users
NGSCB + RIAA = NSA + KGB + CIA. ( R -> K )
From the Transcript of Internet Caucus Panel Discussion. Re: Administration's new encryption policy. Rep. Curt Weldon's statement
Read all of Curt Weldon's statement.Consider that as of 26 August 2003:, There are currently 22 unpatched vulnerabilities in Microsoft's Internet Explorer - many of the serous vulnerabilities Microsoft has not provide a fix to patch the hole in years!
Attestation Monopoly
Microsoft's NGSCB model for DRM content management grants Microsoft effective root digital certificate control over both software and content. It would be a monopoly even stronger than Microsoft's existing desktop dominance. Just as with Microsoft's proprietary file formats and protocols, the network effect would result in any non-dominate player or vendor facing too great a barrier to provide effective monopoly negating free-market competition.
Loss of Fair Use Rights and doctrine of First Sale
Microsoft's NGSCB DRM model also grants content providers far too much restrictive power. For example, in the USA and in most of the world, you are legally allowed to tape broadcast content for later replay ( timeshifting ), gathering evidence for making a complaint, or legitmate research. The DRM model can be used by content providers to circumvent these legal rights. Also if Microsoft or the Codec developer drops support for a format or even a particular digital key, all that content "protected" by that methord or key becomes unreadable.
The DRM model circumvents the Doctrine of First Sale, by side shifting content from being "goods" into a so-called service. When I purchase a DVD, I own that particular physical instance of that DVD and the right to view the content on it. I expect to be able to play that DVD in any DVD player I choose to, including the DVD drive in my Linux system. Also when I have finished viewing that DVD, I expect to be able to pass or even resell that DVD to any party I choose. I might even give that DVD to my local library, and I am legally entitled to do so. As DMCA protected CSS DVDs already limits what you can do with a DVD, Microsoft's plans f
Yes, I'm 100% positive. I used to be a BIOS developer and I have 10 years' experience in device drivers. The whole point behind a modern OS like Linux and Windows 2000/XP is to prevent apps from talking to any hardware resource (and memory and BIOS count as hardware resources) without the OS's permission. An app can't issue an interrupt, nor can it make a call into some fixed memory location in the BIOS. The CPU will just not allow these operations.
And the men who hold high places must be the ones who start
To mold a new reality... closer to the heart
It's good to get a few words on this forum from the voice of experience. Thank you.
As a followup, this and other discussion by BIOS-knowledgeable people would seem to suggest that DRM in the BIOS is not necessarily evil. From the way the design of it was described, it does not appear to prevent you from booting any particular OS you want, but applications may insist on using DRM features.
I know that Linus Torvalds has said that he would accept DRM-aware code in Linux. He's not a fan of DRM (and neither am I), but he sees what the people behind the Phoenix BIOS sees, a marketing opportunity. Someone is going to want this feature, and if Linux does not implement it, it will be left out in the cold.
A DRM-aware Linux OS would not prevent you from installing and running free software. Free software would most likely simply not use the DRM features. Where the problem comes in would be writing free software to interact with, say, streaming audio/video sites. They may insist that the application talking to them be DRM-aware and enforce it by requiring the software to send the BIOS ID/key/whatever, which can be obtained only with a DRM-enabled kernel.
Someone feel free to correct me if any of my assumptions are wrong.
Karma: Frotzed (mostly due to the Frobozz Magic Karma Company)
yeah it boots a 5 year old chipset. Open source BIOS isn't going to happen. Most chipset vendors are extremely secretive about their chipset and by the time the chipset documentation becomes available to Open Source coders, the chipset is already obselete.