[alt.security] Security fix for anonymous uucp

Makey@Logicon.COM (Jeff Makey) (06/13/90)

In article <1990Jun8.134620.24070@cs.rochester.edu> bukys@cs.rochester.edu (Liudvikas Bukys) writes:
>1.  Here's one "minor problem" report: I have heard that .rhosts
>    files have been uucped into ~uucp.  Think about it.

I did think about it for a bit, and then I changed the following
/etc/passwd entry:

    uucp:*:66:1:UNIX-to-UNIX Copy:/usr/spool/uucppublic:

into:

    uucp:*:66:1:UNIX-to-UNIX Copy:/usr/spool/uucppublic:/dev/null
    UUCP:*:66:1:UNIX-to-UNIX Copy:/usr/spool/uucp:

(order is important to preserve "ls -l" output) and changed all
occurrences of "su uucp" in my crontab file into "su UUCP".  This
maintains "~uucp" as a public place to put files, but "su uucp" fails
with a "No shell" error.  Any programs that have a legitimate need to
run with the uucp user id can get to it through the "UUCP" login name,
whose home directory is *not* world-writable.

Sorry for putting this on TCP-IP, but that's where it started.
Followups are directed to alt.security.

                           :: Jeff Makey

Department of Tautological Pleonasms and Superfluous Redundancies Department
    Disclaimer: All opinions are strictly those of the author.
    Internet: Makey@Logicon.COM    UUCP: {nosc,ucsd}!logicon.com!Makey