Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!cmcl2!adm!xadmx!rbj@dsys.icst.nbs.gov From: rbj@dsys.icst.nbs.gov (Root Boy Jim) Newsgroups: comp.unix.questions Subject: tcsh Message-ID: <19805@adm.BRL.MIL> Date: 30 May 89 17:07:42 GMT Sender: news@adm.BRL.MIL Lines: 22 ? From: Jerry Peek ? /etc/shells is there for security. Don't put untested shells in the file. No it's not. It's there for the SA's piece of mind when J. Random Hacker's turbo-charged replacement shell core dumps and he can't log in and has to ask Mr. Root Person to `cp /bin/sh ~jrh/bin/tcrsh' until the next bug. Note that this still allows `echo exit | tee .cshrc .login > .profile'. Perhaps /etc/shells was designed to avoid using a suid or guid shell that I currently cannot execute. If so, then let that be the requirement, or ban suid, gid, and sticky bit files altogether. Much simpler, and more flexible. A reasonable compromise would allow anything in /bin. ? --Jerry Peek; Syracuse University Academic Computing Services; Syracuse, NY ? jdpeek@rodan.acs.syr.edu, jdpeek@suvm.bitnet ? +1 315 443-3995 Root Boy Jim is what I am Are you what you are or what?