From owner-freebsd-security Wed Jun 6 8:30:39 2001 Delivered-To: freebsd-security@freebsd.org Received: from sbtx.tmn.ru (sbtx.tmn.ru [212.76.160.49]) by hub.freebsd.org (Postfix) with ESMTP id 4352B37B406 for ; Wed, 6 Jun 2001 08:30:34 -0700 (PDT) (envelope-from serg@sbtx.tmn.ru) Received: from sv.tech.sibitex.tmn.ru (sv.tech.sibitex.tmn.ru [212.76.160.59]) by sbtx.tmn.ru (8.11.3/8.11.3) with ESMTP id f56FUVI31317; Wed, 6 Jun 2001 21:30:33 +0600 (YEKST) (envelope-from serg@sbtx.tmn.ru) Received: (from serg@localhost) by sv.tech.sibitex.tmn.ru (8.11.3/8.11.3) id f56FUQj00771; Wed, 6 Jun 2001 21:30:26 +0600 (YEKST) (envelope-from serg) Date: Wed, 6 Jun 2001 21:30:26 +0600 From: "Sergey N. Voronkov" To: David Miner Cc: freebsd-security@FreeBSD.ORG Subject: Re: Encrypted passwords Message-ID: <20010606213026.A755@sv.tech.sibitex.tmn.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from david@slis-two.lis.fsu.edu on Wed, Jun 06, 2001 at 11:14:03AM -0400 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Jun 06, 2001 at 11:14:03AM -0400, David Miner wrote: > A while back there was a good discussion on using encrypted passwords to > "automatically" create user accounts. > > I haave a need to create classroom accounts every semester and (borrowing > freely from adduser) created the following perl script. > > But something is not right and I have to go in and manually change the > passwords to what I want. > > The program asks for a password file name and the file contains passwords > that I have approved as meeting my standards. The problem seems to be in > how they get encrypted. > > Suggestions, please? Please look at http://www.FreeBSD.org/cgi/query-pr.cgi?pr=24953 I'v post hook against DES/MD5 encription. Bye, Serg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message