Technology

59627 readers

2807 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

549

NIST proposes barring some of the most nonsensical password rules (arstechnica.com)

submitted 2 months ago by Amicitas@lemmy.world to c/technology@lemmy.world

179 comments fedilink hide all child comments

Here is the text of the NIST sp800-63b Digital Identity Guidelines.

you are viewing a single comment's thread
view the rest of the comments

[–] cmnybo@discuss.tchncs.de 20 points 2 months ago (14 children)

Any password length (within reason) and any character should be allowed. It's going to be hashed and only the hash will be stored right? Length and character limits make me suspect it's being stored in plain text.

[–] frezik@midwest.social 12 points 2 months ago (1 children)

Rules here are 64 as a reasonable maximum. A lot of programmers don't realize that bcrypt and scrypt max at 72 bytes (which may or may not be the same as 72 characters). You can get around it by prehashing, but meh. This is long enough even for a reasonable passphrase scheme.

[–] daddy32@lemmy.world 6 points 2 months ago

Minor note: 64 unicode characters is potentially much more than 72 bytes.

load more comments (12 replies)