[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD7EdQZhy4TObWugNc8i5oipZo8+or78h+=6+sU-3s39RC7O_w@mail.gmail.com>
Date: Thu, 15 Dec 2016 15:58:09 +0100
From: Martin Rublik <martin.rublik@...il.com>
To: passwords@...ts.openwall.com
Subject: proposed NIST guidelines on passwords
Hi,
NIST published new draft on Digital Authentication Guidline
https://pages.nist.gov/800-63-3/sp800-63b.html#memorized-secret-verifiers
Summary related to passwords is following:
- at least 8 chars minimum length
- at least 64 chars should be allowed by application
- printing ASCII, space and UNICODE allowed (the application should perform
normalization, little worried about this one)
- password hints should not be implemented,
- passwords should be checked by the application against: passwords
obtained from breaches, dictionary words, context specific such as
username. These passwords should not be allowed / user should be warned
- no composition rules such as different character sets
- no periodic change (unless a breach was detected)
- mandatory encryption/hashing (PBKDF2 mentioned)
Martin
Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
