News for hackers. Stuff that matters.
Re:Microsoft doesn't allow passwords greater than 16 charact... by rogerbinns on Wednesday August 15, 2012 @10:28PM (#4389629)
The passwords should be salted and then hashed. The hash produces the same length output no matter how long the input. Consequently length limitations are either UI/protocol limitations, or because salting and hashing is extremely poorly done. My money is on the latter.
Re:Microsoft doesn't allow passwords greater than 16 charact... by lrei on Wednesday August 15, 2012 @10:55PM (#4389704)
I know. But yes I was thinking that the password still has to go through UIs (Web & Native), be sent over the network and read by the server and only than can it be hashed and compared to the stored hash.

I agree it sounds weird especially since I guess everything is done on top of .NET and JS. Neither of which is likely to suffer from buffer overflows nor would whatever protocols they use have problems transporting large strings with non-ASCII chars. And I don't any other technical problems that might cause.

But there has to be a reason. I guess it's possible someone was overzealous or screwed up. Maybe it was because it would be too hard to type it on an Xbox? Doesn't sound very plausible though.

I doubt that MS is doing password hashing wrong - it's not hard to begin with and they probably learned their lesson from the NT days when they implemented p.hashing poorly and it led to the NT passwords being easy to brute force.

Re:Microsoft doesn't allow passwords greater than 16 charact... by rogerbinns on Thursday August 16, 2012 @04:02PM (#4393383)
> I doubt that MS is doing password hashing wrong

They have a long and storied history of doing just that. You can get a flavour from http://en.wikipedia.org/wiki/NTLM

Their hashing is most likely something defined to produce two parts from two 8 character chunks.