From owner-freebsd-hackers Tue May 6 16:47:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA14113 for hackers-outgoing; Tue, 6 May 1997 16:47:21 -0700 (PDT) Received: from aries.bb.cc.wa.us ([208.8.136.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA14100 for ; Tue, 6 May 1997 16:47:11 -0700 (PDT) Received: from localhost (chris@localhost) by aries.bb.cc.wa.us (8.8.5/8.6.9) with SMTP id QAA03110 for ; Tue, 6 May 1997 16:41:16 -0700 (PDT) Date: Tue, 6 May 1997 16:41:16 -0700 (PDT) From: Chris Coleman To: hackers@freebsd.org Subject: Passwords don't work. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just upgraded to 3.0-05021997-SNAP and it fixed my syscons problem. :-) (otherwise i couldn't have upgraded.) I upgraded from a 2.1.6 machine. However, about half of my users can't login in because their passwords don't work. I noticed that it is all the newer ones. All the ones that have been around for more than three months still work. I think it must have something to do with a different encryption type. As far as I know I haven't changed. But I could be wrong. Right now we are just changing users passwords as they complain. (really sucks with 300+ students) Any suggestions would be appreciated. Christopher J. Coleman (chris@aries.bb.cc.wa.us) Computer Support Technician I (509)-766-8873 Big Bend Community College Internet Instructor FreeBSD Book Project: http://vinyl.quickweb.com/~chrisc/book.html Disclaimer: Even Though it has My Name on it, Doesn't mean I said it.