home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.security.misc
- Path: sparky!uunet!usc!sdd.hp.com!elroy.jpl.nasa.gov!dank
- From: dank@blacks.jpl.nasa.gov (Dan Kegel)
- Subject: Re: unhappy about overloading finger
- Message-ID: <dank.711867106@blacks.jpl.nasa.gov>
- Sender: news@elroy.jpl.nasa.gov (Usenet)
- Nntp-Posting-Host: blacks.jpl.nasa.gov
- Organization: Image Analysis Systems Group, JPL
- References: <ggm.711690458@brolga> <199207230140.AA18677@fnord.wang.com> <1992Jul23.032058.3292@reed.edu>
- Date: Thu, 23 Jul 1992 04:51:46 GMT
- Lines: 15
-
- nelson@reed.edu (Nelson Minar) writes:
- >A far more common way for accounts to be cracked is for someone to
- >steal your YP password file (not too hard to do if you're running yp
- >and are on the internet) and run a fine cracking tool like Crack 4.1
- >with a fast crypt().
-
- >How do you, as a sysadmin, prevent this? Crack your password file
- >yourself. Don't let users have crackable passwords.
-
- >If you want to be butch try to fix yp, or use a shadow scheme that
- >works. That's a lot of trouble, and the best you'll probably do is
- >security through obscurity.
-
- With Sun's latest patches, YP is supposed to be fairly secure;
- nobody can get your passwd map that you don't want to.
-