From owner-freebsd-security@freebsd.org Wed May 23 21:40:32 2018 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90B82EE6DFA for ; Wed, 23 May 2018 21:40:32 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3A736804CF for ; Wed, 23 May 2018 21:40:31 +0000 (UTC) (envelope-from feld@FreeBSD.org) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 82F4721EDD for ; Wed, 23 May 2018 17:40:31 -0400 (EDT) Received: from web4 ([10.202.2.214]) by compute3.internal (MEProxy); Wed, 23 May 2018 17:40:31 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=jyTSa2pj+/aixrpq92fDtggqip6xw Fa4MArA2vllpNc=; b=TIlsvLjPFaBPjlKUT6wQ5AetDLmjmDLiN95VbhGnNrLJW VjNQi8sVkPffPjAbElCf5pjmR2UUoHGDa5pjMHS241RbBd/YI+fkcNy2wTAB2mN7 7TOgHD8WdE2CgqvNMxNogQcHZQ+0K1K07m1hiupt6ezTzdt+Wu69jhr0BmbZKFmX u62aFh+NX6rYpFjgcIPVwc2l3K2VMXC0DNHFny+BkbdUfccAm7jOOsG12arZdJWw jwCRX/ovxPrulCc2UKdAfgnTOSfIH3wGZaJWbC2jnyv8bLC6dnZgaUIIERTIbdnJ fA3A0auCCAGIrMsTpk5B8Kd9zNSdMFoUMBcGXY/4g== X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Proxy: X-ME-Sender: Received: by mailuser.nyi.internal (Postfix, from userid 99) id 29E1EBA781; Wed, 23 May 2018 17:40:31 -0400 (EDT) Message-Id: <1527111631.2205598.1382649664.0BF85F15@webmail.messagingengine.com> From: Mark Felder To: freebsd-security@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="utf-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-a224ff37 Date: Wed, 23 May 2018 16:40:31 -0500 Subject: Default password hash, redux X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2018 21:40:32 -0000 Around 2012[1] we made the brave switch from md5crypt to sha512. Some people were asking for bcrypt to be default, and others were hoping we would see pbkdf2 support. We went with compatible. Additionally, making password hashing more In light of this new article[2] I would like to rehash (pun intended) this conversation and also mention a bug report[3] we've been sitting on in some form for 12 years[4] with usable code that would make working with password hashing algorithms easier and the rounds configurable by the admin. I'd also like to see us to pull in scrypt if cperciva doesn't have any objections. It's good to have options. PS: Why does "compatibility" matter for a default algorithm? Having a default different than Linux or Solaris isn't a bad thing as long as we implement the industry's common hashes which would permit any management tools twiddling the master.passwd manually to still be able to insert the password hashes in a common format... [1] https://lists.freebsd.org/pipermail/freebsd-security/2012-June/006271.html [2] https://pthree.org/2018/05/23/do-not-use-sha256crypt-sha512crypt-theyre-dangerous/ [3] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=182518 [4] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=75934 is the original report about the issue -- Mark Felder ports-secteam & portmgr member feld@FreeBSD.org