3 ms·
I talked to a guy that worked on Windows Live about the 16 char restriction. Microsoft Accounts also do not support Unicode, or anything but a small subset of A
by MichaelGG 14y ago
I talked to a guy that worked on Windows Live about the 16 char restriction. Microsoft Accounts also do not support Unicode, or anything but a small subset of ASCII characters.
First, there must be a maximum size. Obviously, you're not going to allow allow 2^64 byte passwords. So it's under that. But, sure, 16 characters is pretty low.
The actual reason seems to be lost to time. The password code was originally written well over a decade ago, when things were less security focused. For all we know, some part of the auth pipeline (even if the passwords are stored hashed) might have sent the user data in a space or comma delimited, using 8-bit chars without UTF-8 support.
He explained that every time they've reviewed it, the password restrictions haven't been close to the top of things they can spend their time on to improve user safety.
I've run into other companies that limit symbols, citing problems with users on mobile devices messing up and generating support tickets. That sounds reasonable for lower-security assets.
Evernote's space explanation sounds really silly. Why not just include stripping spaces as part of the password "hash" function? That's gotta be easier than using Regex.
I remember reading a story about Facebook, where they flipped-case hashes as well, again to help the user login experience.
- rogerbinns 14y agoThe general reason in Microsoft environments is backwards compatibility. They have had a number of password hashing schemes over time, each getting better. But the password itself isn't sent in the clear over the wire so there is no way to upgrade the user account from one hash to another. The only time it can be done is when the user changes their password, and again that requires the authentication service getting the new password in the clear. Consequently they tend to store all supported hashes at once, and you are limited to the lowest common denominator. http://en.wikipedia.org/wiki/LM_hash http://en.wikipedia.org/wiki/LM_hash http://en.wikipedia.org/wiki/NTLM#NTLMv1 http://en.wikipedia.org/wiki/NTLM#NTLMv1 http://support.microsoft.com/kb/299656 http://support.microsoft.com/kb/299656
- jfb 14y agoApple truncates passwords longer than 32 characters on Apple ID creation. I find this really annoying, particularly because they don't call this restriction out when you create/change a password. I think it'd be nice if there were a list of these stupid password rules per domain; that way, 1Password and equivalents could generate maximally strong random passwords per site. Best of all, of course, would be a standard, machine-readable way to communicate this security brain-damage so that it wouldn't have be crowdsourced. Hmm.