News for hackers. Stuff that matters.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by rplnt on Tuesday January 08, 2013 @11:18AM (#5026885)
Can email interfere with HTTP headers though? There's no \r\n, ";" or "=" in valid email.

Anyway, I have seen sites where it was used as a security measure. Or so the authors thought I guess. Storing login password in url parameter? Seems safe if it is encoded.. But it was years ago.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by hoov on Tuesday January 08, 2013 @11:43AM (#5026993)
Actually, the '=' character is allowed. [1]

[1] http://tools.ietf.org/html/rfc5322#section-3.2.3

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by ddunkin on Tuesday January 08, 2013 @12:49PM (#5027317)
It sounds like you confused encoded with encrypted, encoded is no different than plain-text. The encoding is just to get a valid string for the URI (so a password can contain special URI characters) and is instantly reversible.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by rplnt on Wednesday January 09, 2013 @03:56AM (#5030769)
No, I haven't. Should have put the "security measure" in the quotes.
Re:How I Hacked Facebook’s Secure Files Transfer Service for... by papsosouid on Tuesday January 08, 2013 @02:33PM (#5027973)
>There's no \r\n, ";" or "=" in valid email.

Both ; and = are perfectly valid.

Re:How I Hacked Facebook’s Secure Files Transfer Service for... by rplnt on Wednesday January 09, 2013 @04:00AM (#5030779)
Did not know that, thanks for pointing that out. In that case the encoding is necessary. On top of that I just found out that even Unicode characters are permitted (RFC 6531).