From owner-freebsd-questions@FreeBSD.ORG Sun Jul 10 02:14:52 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED93516A41C for ; Sun, 10 Jul 2005 02:14:52 +0000 (GMT) (envelope-from jeff.dyke@gmail.com) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C14A43D45 for ; Sun, 10 Jul 2005 02:14:52 +0000 (GMT) (envelope-from jeff.dyke@gmail.com) Received: by rproxy.gmail.com with SMTP id c16so585941rne for ; Sat, 09 Jul 2005 19:14:52 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:reply-to:user-agent:x-accept-language:mime-version:to:subject:content-type:content-transfer-encoding:from; b=AY2tEGRpnyU4uJsX9cJdQsjUZdxXwpehD788IF4UWocZFDvisfCeOCdcs8R1pUjQqpm2rDiQCzuqXL2fT3H6nu4B35XVbSCsKCPZN/NONBHL7jL56EA0ac61nQm99WEhFYzDqjaAP5EEnWcZJAwN/OUyIAPh6AaCEFSm5bQGi1I= Received: by 10.38.98.76 with SMTP id v76mr3105707rnb; Sat, 09 Jul 2005 19:14:51 -0700 (PDT) Received: from ?192.168.15.100? ([66.31.74.215]) by mx.gmail.com with ESMTP id g2sm4310082rne.2005.07.09.19.14.51; Sat, 09 Jul 2005 19:14:51 -0700 (PDT) Message-ID: <42D08423.5080401@azimapower.com> Date: Sat, 09 Jul 2005 22:12:51 -0400 User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit From: Jeff Subject: password rotation and unique constraint X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jdyke@azimapower.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jul 2005 02:14:53 -0000 i'd like to configure pw.conf to force password expiration. is there anyway to ensure the user can not change it to the same password. i don't need to keep the last 7 or anything, just stop it being the same from the last one. If/when i need the last N password, i'd assume i'd have to move to LDAP? running 5.4-RELEASE Thanks jeff