This message is from the T13 list server.
DCO could certainly require you to toss the drive. (Note, I said could, it would depend on what was DCO'd) Not all BIOS's implement it because it's a market decision for them. (Each OEM / channel manufacturer has different requirements or target environments). You're more likely to find that an OEM system that does this than a channel MB. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas Jansen Sent: Monday, May 16, 2005 10:35 AM To: Curtis Stevens; [email protected] Subject: Re: [t13] Security problems This message is from the T13 list server. Curtis Stevens wrote: >I was involved in the creation of this command set. There was much >discussion around the possibility of a virus being able to lock a drive. >There are already many ways to destroy data on the drive. This has not >offered anything really new. It has also been around for almost 10 years, >so it is a little late to be complaining. When security was introduced, I >was working for a major BIOS vendor and know for a fact that at that time >AMI, Phoenix, and Award implemented the FREEZE LOCK. This was done because >of the virus threat. If you have found a system that does not issue the >freeze lock, then I would say that you have a substandard system and you >should return it for one that actually works. > > There are many ways to trash a drive with one command including >SETMAX, DCO, Writing the media, and security. I am surprised that you are >complaining about security, that is really the least of the threats... > > > Would any of those require me to throw the disk away? I understand that the data is always at risk but security even puts my hardware on risk. This discusion is not data only! By the way they must have forgotten something at the BIOS. I have a brand mainboard with an AMI Bios. I guess it's two years old. Sincerely, Thomas
