Path: utzoo!utgpu!watmath!watdragon!rose!ccplumb From: ccplumb@rose.waterloo.edu (Colin Plumb) Newsgroups: comp.sys.amiga Subject: Re: another 1.4 suggestion Keywords: RAD:/VD0:, Write Protect Message-ID: <16674@watdragon.waterloo.edu> Date: 25 Sep 89 22:12:39 GMT References: <10156@bsu-cs.bsu.edu> Sender: daemon@watdragon.waterloo.edu Reply-To: ccplumb@rose.waterloo.edu (Colin Plumb) Organization: U. of Waterloo, Ontario Lines: 18 In article <10156@bsu-cs.bsu.edu> aegnor@bsu-cs.bsu.edu (David C. Powell) writes: >The ability to 'write protect' the RAD: and/or the VD0: >could this possibly be added via an INFO select in 1.4? I still use >Transformer, and with RAD: in place, it survives, but SOME of its files >get 'overwritten' making it have R/W errors. I know Transformer would >probably still do this, but other things (VIRI) would have a semi-hard >time (IMHO) if they 'see' the RAD: as being READ-ONLY. There already is such a command in 1.3. CLI-only, at the moment. You supply a passkey (a 32-bit number) and must supply the same one to unlock the volume. I do not believe the protection survives reboots. Note that a 1.3-aware virus could extract the key from the system, and anything could hit the trackdisk.device directly. I forget the name (I don't have my 1.3 manual handy), but I've implemented it... -- -Colin