From owner-freebsd-security@FreeBSD.ORG Sat Jun 9 20:16:56 2012 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF3511065673 for ; Sat, 9 Jun 2012 20:16:56 +0000 (UTC) (envelope-from rsimmons0@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6736E8FC0C for ; Sat, 9 Jun 2012 20:16:56 +0000 (UTC) Received: by vcbfy7 with SMTP id fy7so1885902vcb.13 for ; Sat, 09 Jun 2012 13:16:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=2/tVqfQmSqXd/ARUwGP5OoiTrIZ07JpJol3jHOVWybE=; b=WHG9IXQ9SxewvQqgDKesP76LfEoaaTYasq3bgz7A7TDLm7HXB/HXsC6Jt8tY5qbkut OeT2pathZmw0sg9Y2Js+wNgQ8oeUXcvyUXPmhJ2775HU4OfWaPj5BRZowjCa9EAPOSPb 2Wc7Qa0DEN04OXwohEdmQPWFP9Pti57fNigeJhRewN5OIhS93nKDtIUhS52GrtI96735 0xb6IYEuxMZLeYY+E8ohARSlIlwng/AKDTmcObmOeFX3PmsslWCr6xAxtWZAMmCKsCCO 1B5IDtNWxkubYZSA8tSzd+bhfWgIb1T3dQ89y36upB0eUquYb3cXaUWKOZ9dLXaC++xv DF3g== MIME-Version: 1.0 Received: by 10.52.88.234 with SMTP id bj10mr8160999vdb.48.1339273015713; Sat, 09 Jun 2012 13:16:55 -0700 (PDT) Received: by 10.52.113.97 with HTTP; Sat, 9 Jun 2012 13:16:55 -0700 (PDT) In-Reply-To: <4FD350EF.6080802@sentex.net> References: <86r4tqotjo.fsf@ds4.des.no> <4FD334BE.4020900@sentex.net> <4FD350EF.6080802@sentex.net> Date: Sat, 9 Jun 2012 16:16:55 -0400 Message-ID: From: Robert Simmons To: freebsd-security@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: Default password hash X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Jun 2012 20:16:56 -0000 On Sat, Jun 9, 2012 at 9:34 AM, Mike Tancsa wrote: > On 6/9/2012 9:19 AM, someone wrote: >> hi, >> >> what is needed to change from md5 to sha512 ? As all old passwd are md5, I imagine there is a >> sequence of steps not to lock me out of the box. is there any place that documents this ? > change the users passwd to something new, or just use the old passwd, > but re-enter it Bad idea. Never reuse an old password.