From owner-freebsd-questions@FreeBSD.ORG Wed May 7 21:49:30 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37C2E106564A for ; Wed, 7 May 2008 21:49:30 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from snoogles.rachie.is-a-geek.net (rachie.is-a-geek.net [66.230.99.27]) by mx1.freebsd.org (Postfix) with ESMTP id 027A98FC1B for ; Wed, 7 May 2008 21:49:29 +0000 (UTC) (envelope-from fbsd.questions@rachie.is-a-geek.net) Received: from localhost (localhost [127.0.0.1]) by snoogles.rachie.is-a-geek.net (Postfix) with ESMTP id B39E41CD4A; Wed, 7 May 2008 13:49:28 -0800 (AKDT) From: Mel To: freebsd-questions@freebsd.org Date: Wed, 7 May 2008 23:49:25 +0200 User-Agent: KMail/1.9.7 References: <75a268720805071400o2eb75c54y77c11790407cf045@mail.gmail.com> <200805072316.26068.fbsd.questions@rachie.is-a-geek.net> <75a268720805071423v44b3450cj65c36e1af70c4a5@mail.gmail.com> In-Reply-To: <75a268720805071423v44b3450cj65c36e1af70c4a5@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200805072349.26929.fbsd.questions@rachie.is-a-geek.net> Cc: Omer Faruk Sen Subject: Re: minpasswordlen and login.conf not working on 6 or 7 series X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 May 2008 21:49:30 -0000 On Wednesday 07 May 2008 23:23:54 Omer Faruk Sen wrote: > Actually I have read it but haven't read all the man pages because > even in 7.0 manual page for login.conf still have: > > minpasswordlen number 6 The minimum length a local password may be. > > I think that line should be removed from manual page too. It's confusing, but... The following capabilities are reserved for the purposes indicated and may be supported by third-party software. They are not implemented in the base system. So this basically means, that cap_mkdb /etc/login.conf will not throw an error when it sees that capability and it will also set the default value, if applicable. Programs can use getcap(3) to consult the value. For instance you could write your own login program, or consult and enforce it through a webpage, or implement it in a server program. -- Mel Problem with today's modular software: they start with the modules and never get to the software part.