We've noticed that you've been inactive for over 10 minute(s). We've stopped running the Shoutbox due to your inactivity. If you are back again, please click the I'm Back button below.
use your bios settings;
1. set to ONLY boot from your hd;
2. set passwords for your bios.
get that? now nobody can boot your system using other boot disk/cd. it cannot be breached. the only people that can override that are the one who have physical access to the servers and able to reset the CMOS jumpers.
I know the exploit is not a new one. I have bios password on all the xp computers at work due to this exploit.
Thanks for the link to one of the articles.
For an OS that are supposed to be security oriented I consider this a flaw. My place of work are considering removing all the cd / dvd players in user pc's and the 3.5" disks are gone in most og them also.
For a home school environment it may not be a flaw, for work it's a flaw. I can hang out after hours and hack someone elses computer ! (Wait! I can do that I"m the admin... ) As for security flaws, I hate all the messenger programs that are in use.. .
Ehm dude? I don't see the flaw? If i want to get on a NTFS partition I boot Knoppix with NTFS support, it even boots from floppy. If you have physical access to the computer and the data is NOT encrypted, chances are that 99 out of 100 times you can at least READ the data. Booting another OS would do, or the w2k boot disc.
Anyways, this so called 'exploit' was found quite a while ago.
AS for windows XP, The bootdisks purposely access the part of the drive and check if the system is accessible, and if it is, it is designed to ask for authorisation.
I think you just said the solution, "if the system is accessible" xp does it for xp w2k does it for w2k. I have not tried the other way around.. I have a w2k server that is scheduled for a restart this weekend. I'll try to put the xp recovery disk in it to see if it bypasses the password sequence.
what is it looking at to deem it accessible? a registry key? add one for w2k. Does it check bios? I have to read up on that. I have the resource kit documentation for xp pro so maybe I can find something there.
As for a point... off course you can have a point....
The solution are a patch that chagnes the permission for boot disks, xp works in XP. w2k works in w2k both are password protected. There should be an easy task to add code for the xp os to prompt for a password when w2k is in the cd drive. The technology is already there to prompt for a pwd it's already working for xp
aah.. I am confused. I dont think there are any files in HDD which grant access to these CD's.. If there is, the patch is possible. But if the files on the HDD make no diffrence for the Bootdisk. The bootdisk can work its way out to the data and open the way for people to access it.
AS for windows XP, The bootdisks purposely access the part of the drive and check if the system is accessible, and if it is, it is designed to ask for authorisation.
You are right, if you pop a XP disk in the recovery console it asks for the Administrator password. Pop the W2k disk in and you start the W2k recovery console and bypass the whole XP system including passwords on files and folders.
The solution are a patch that chagnes the permission for boot disks, xp works in XP. w2k works in w2k both are password protected. There should be an easy task to add code for the xp os to prompt for a password when w2k is in the cd drive. The technology is already there to prompt for a pwd it's already working for xp.
Turn on the BIOS Password with a BIOS password in place the CD can not bypass and boot your computer. So until M$ releases a patch for this flaw, turn on BIOS password and make sure it's not the same as your regular password and store it in a secure place.
I wonder if Microsoft can actually release a Patch for this one.
I assume that the Boot disk does not interfere with the boot files already stored on the system. It loads up in memory seperately and accesses the drive and there is absolutely nothing between its path to stop it and ask for authorisation. And may be because of this, the other security systems except EFS failed. So until and unless those files are not encrypted, developing a patch for the above flaw is difficult.
The patch that will be released will have to protect the files compltely just like EFS. So instead of developing a new system altogether for encryption, microsoft might go with the EFS thing. So in the next patch, microsoft may decide to enable EFS for WinXP home edition which is again going to cost microsoft a lot.