QUOTE(Ray2Kay @ Feb 11 2007, 05:43 AM)

man give them a idea..........thats a nice right out.
1. check that responses vary appropriately between challenges of the same type == Let's hope that the DVD drive in the box is in it's theoretical best working condition. Even if the drive isn't hacked, some drives are extremely slow to pull out data off a disc, so should those drives be banned? --> Unhacked & hacked drives are affected
2. use same debug commands to load disc-specific hashing code into drive, check for patched firmware == Let's send some commands to the drive and see what happens; a. The cheap drive isn't working like it should and sends some error code or hangs the system b. The drive is hacked and prevents this from happening --> Unhacked & hacked drives are affected, they could even brick some drives with this.
3. look for SS.bin file via host or code loading into drive == Rename SS.BIN

. I doubt they can spy on the SS -data that is loaded from the disc (where it's located). Is the SS.BIN even stored as SS.BIN in the media when burned? Or is it just plain data. I really don't get how "looking for a file" would help if it's plain data to begin with.
I think that "effort/$" is not in m$'s favor.