home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!lll-winken!fnnews!fncrd6.fnal.gov!rohrer
- From: rohrer@fncrd6.fnal.gov (Keith Rohrer)
- Newsgroups: comp.os.linux
- Subject: Re: Linus security/Non root access
- Message-ID: <2213@fnnews.fnal.gov>
- Date: 21 Aug 92 14:54:34 GMT
- References: <1409@yetti.UUCP> <1992Aug21.020626.20221@unislc.uucp> <qwdpbp0y@cck.coventry.ac.uk>
- Sender: news@fnnews.fnal.gov
- Organization: Fermilab
- Lines: 31
- Nntp-Posting-Host: fncrd6.fnal.gov
-
- In article <qwdpbp0y@cck.coventry.ac.uk> csg203@cck.coventry.ac.uk (Bluebeard) writes:
- [much deleted]
- >
- >But that wouldn't stop someone with linux/minix boot and root file system
- >disks, booting from floppy and then mounting the hard disk.
- >
- >The protected BIOS is the only real answer unless the linux partition was
- >encoded in some way that only the 'official' kernel could read.
- You could always hack your copy of the kernel's filesystem routines to do some-
- thing like always use the negative of one of the essential paramters in the
- filesystem, though changing over would be a nuisance.
-
- But the best I've seen is something like my 5-5-91 AMI BIOS, which lets you
- define the drive boot order a-c or c-a. Set passwording on changing setup,
- set c to boot first, and as long as c is bootable a won't be checked to boot
- off of. Unless they scribble on your hard drive's boot sector, it will always
- boot to Linux...
-
- >--
- >***********************************************************************
- >* FLESH: Charlie Freckleton * JANET: csg203@uk.ac.cov.cck *
- >* ALIAS: Bluebeard * or : stliaise@uk.ac.cov.cck *
- >***********************************************************************
-
- Keith
- (rohrer@fncrd0.fnal.gov)
- --
- Disclaimer: None of Grinnell College, URA, Fermilab, and any other affiliated
- persons or orginizations have licensed my ideas or opinions, and thus are
- not entitled to any which may appear above.
-
-