From owner-cvs-all  Wed May  2  6:20:18 2001
Delivered-To: cvs-all@freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8240637B43C; Wed,  2 May 2001 06:20:13 -0700 (PDT)
	(envelope-from adrian@FreeBSD.org)
Received: (from adrian@localhost)
	by freefall.freebsd.org (8.11.1/8.11.1) id f42DKDR50818;
	Wed, 2 May 2001 06:20:13 -0700 (PDT)
	(envelope-from adrian)
Message-Id: <200105021320.f42DKDR50818@freefall.freebsd.org>
From: Adrian Chadd <adrian@FreeBSD.org>
Date: Wed, 2 May 2001 06:20:13 -0700 (PDT)
To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject: cvs commit: src/usr.sbin/adduser adduser.perl
X-FreeBSD-CVS-Branch: HEAD
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

adrian      2001/05/02 06:20:13 PDT

  Modified files:
    usr.sbin/adduser     adduser.perl 
  Log:
  Extend adduser to create "locked" accounts. Adduser can now lock an
  account at creation, create accounts with a "*" password (so you can
  use alternate authentication schemes without fearing a "default" password
  biting you later), and blank passwords.
  
  Yes, adduser could create a blank password account, but this makes it
  slightly more difficult to shoot yourself in the foot.
  
  The /etc/adduser.conf entries are:
  
  # use password-based authentication for new users
  # defaultusepassword =  "yes" | "no"
  defaultusepassword = "yes"
  
  # enable account password at creation
  # (the password will be prepended with a star if the account isn't enabled)
  # defaultenableaccount = "yes" | "no"
  defaultenableaccount = "yes"
  
  # allow blank passwords
  # defaultemptypassword = "yes" | "no"
  defaultemptypassword = "no"
  
  Requested by: alfred
  Reviewed by: alfred
  
  Revision  Changes    Path
  1.46      +138 -16   src/usr.sbin/adduser/adduser.perl


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message