Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sample.eng.ohio-state.edu!purdue!mentor.cc.purdue.edu!sage.cc.purdue.edu!asg From: asg@sage.cc.purdue.edu (The Grand Master) Newsgroups: comp.unix.amiga Subject: Re: Secure floppy filesyetms (was Re: interesting feature on AMIX..) Message-ID: <14013@mentor.cc.purdue.edu> Date: 26 Jun 91 18:19:24 GMT References: <2761@amix.commodore.com> Sender: news@mentor.cc.purdue.edu Reply-To: asg@sage.cc.purdue.edu (The Grand Master) Organization: Purdue University Lines: 25 In article <2761@amix.commodore.com> ag@amix.commodore.com (Keith Gabryelski) writes: }dillon@overload.Berkeley.CA.US (Matthew Dillon) writes: }> There is no way to secure a floppy. } }Sure there is: one rule must be followed, though. If a user mounts a }filesystem then set[ug]id or device files on that fileystem should not work. } }Pax, Keith That is not all. Device files must also be ignored. What if I use my Amiga3000UX at home and create a floppy with a device file that has the device numbers of /dev/kmem, and then make it 777. (It would be in my uid and not suid). Now I have a way to alter and/or poke throught kernel memory no? So device files must also be ignored. Bruce --------- ### ## Courtesy of Bruce Varney ### # aka -> The Grand Master # asg@sage.cc.purdue.edu ### ##### # PUCC ### # ;-) # # ;'> # ##