Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!mcsun!ukc!mucs!logitek!grep!frank
From: frank@grep.co.uk (Frank Wales)
Newsgroups: comp.unix.questions
Subject: Re: Password security (was Re: comp.unix.wizards)
Message-ID: <1990Dec12.150540.22053@grep.co.uk>
Date: 12 Dec 90 15:05:40 GMT
References: <1990Dec8.215719.15358@IRO.UMontreal.CA> <1990Dec10.153246.6297@smsc.sony.com>
Reply-To: frank@grep.co.uk (Frank Wales)
Organization: Grep Limited, LEEDS, UK
Lines: 12

In article <1990Dec10.153246.6297@smsc.sony.com> dce@smsc.sony.com 
(David Elliott) writes:
>Then again, if you are writing a secure program, it's almost certain
>that the program will be setuid or setgid, in which case you can
>protect the program from being read by anyone other than that uid
>or gid.

Stop anyone at all from reading a binary executable (except the super-user)
with chmod -r, and it will still work; readability doesn't matter.
--
Frank Wales, Grep Limited,             [frank@grep.co.uk<->uunet!grep!frank]
Kirkfields Business Centre, Kirk Lane, LEEDS, UK, LS19 7LX. (+44) 532 500303