>>> Brad Hards <[EMAIL PROTECTED]> 04/15/00 04:20AM >>>
> A post on linux-security also stated that it may be possible
> to beat the write protect with a read-write disk, a needle
> (to force eject), and the write protect disk, which you just
> put in after ejecting the read-write disk. Apparently the Zip
> disk doesn't recheck the permissions.
If you ever find a situation where this does work, be aware, you haven't just defeated
the write-protect code ... you've also defeated the defect management cache. What
that means is that x200 byte blocks of data may appear, disappear, shift at random in
both disks involved. Or not. You could even end up with the heads positioned on
tracks marked as bad places to sit back in the original factory format. An extremely
uncontrolled stimulus: akin to falsely marking dirty host caches clean at random.
x4402 Pat LaVarre of iOmega [EMAIL PROTECTED] http://members.aol.com/ppaatt/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
