From owner-freebsd-security@freebsd.org Wed May 23 21:50:17 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 EBBA4EE8B3B for ; Wed, 23 May 2018 21:50:16 +0000 (UTC) (envelope-from yonas@fizk.net) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6ACB280D48 for ; Wed, 23 May 2018 21:50:16 +0000 (UTC) (envelope-from yonas@fizk.net) Received: by mail-wm0-x236.google.com with SMTP id q4-v6so4876540wmq.1 for ; Wed, 23 May 2018 14:50:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fizk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VDQXH8yvYcTyetUdZA1GIbv6FCbhaGHRqVd95sxYYUs=; b=BqXRHgJr9yMDnGjxrb+3lchh7WMNcp3DqivONohykWLqC8gukLATGL3KV2O8UPFYe4 1T4NOU8Qr27PNxur4HKa1HvG8cPBlEnz1AMQhmMijSYGhG4Z6lCunmrZFcfxkbprtEOs wbjjcmCbKPXs7r//gVjEzIO0ZuoMQVLKbpyZA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=VDQXH8yvYcTyetUdZA1GIbv6FCbhaGHRqVd95sxYYUs=; b=IgaK2y0pHJCxPafUeQQSPSrqyH0082Ny6pnMVL26LfD5jThsyjINxCPWw5Od4zKXs7 Jl3OatLxxJvfe3gnqoyF2S07LUdwUmygWODqD8jJDuhLSk8F5FfgjN94iPiwrIZPAC5v 95TQanHO/mp+O9YLwwTbRGbZZT5G7zje7omDH53mfVBA3WF0MahIUrrQJPGlx5FaLHgM Jjx88lHYSc/Oj94tKqi0MygkzMmzGt8UGYNHC1VSnxYMsktqmD9vPDw10kUHeS3NiqNT yRbi47VqWFXP2iSIOvb0dxPVdaRpqOTKAkbyYYc+0jnXyuYb1lbWn+QihZnOCW+/5dv6 4OvA== X-Gm-Message-State: ALKqPwdyDfRxAeFR/cdMInIxbe6kDpalee0wNxJ2kME95ynN4q3C9/AA GXdChpkwGFN2cs3C78vBZw2srb012LvRlUkMXFbzOA== X-Google-Smtp-Source: AB8JxZpAAUgYVoGuhYJOiNFiXKnxtAwBh0Af94Nz2d6gCnu4aF0EUspEWD/CDW6V7rqkNB6mcLXkwFAyWb+pOcgQo9Y= X-Received: by 2002:a1c:aa55:: with SMTP id t82-v6mr5451433wme.78.1527112215407; Wed, 23 May 2018 14:50:15 -0700 (PDT) MIME-Version: 1.0 References: <1527111631.2205598.1382649664.0BF85F15@webmail.messagingengine.com> In-Reply-To: <1527111631.2205598.1382649664.0BF85F15@webmail.messagingengine.com> From: Yonas Yanfa Date: Wed, 23 May 2018 17:50:04 -0400 Message-ID: Subject: Re: Default password hash, redux To: Mark Felder Cc: freebsd-security@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.26 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:50:17 -0000 I recommend adding support for Argon2. https://en.wikipedia.org/wiki/Argon2 On Wed, May 23, 2018, 5:42 PM Mark Felder, wrote: > 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 > _______________________________________________ > freebsd-security@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org > " >