News for hackers. Stuff that matters.
Re:LinkedIn Intro: Doing the Impossible on iOS by annnnd on Thursday October 24, 2013 @08:14AM (#6604745)
DON'T! Just don't.

Encrypting user credentials in JS is probably even worse than parsing HTML with regular expressions: http://stackoverflow.com/questions/1732348/regex-match-open-...

Just send it in cleartext, but over properly verified https.

Re:LinkedIn Intro: Doing the Impossible on iOS by mr_luc on Thursday October 24, 2013 @09:02AM (#6604978)
I've read the Matasano whitepaper on why you can't count on Javascript for security, as I imagine you have, and it makes sense. Use https.

That being said, look at something like blockchain.info.

It adds javascript security on top of https, and for (what seems like) excellent reasons.

Re:LinkedIn Intro: Doing the Impossible on iOS by nopassrecover on Monday October 28, 2013 @12:13AM (#6625100)
I was just musing hypothetically, but can you elaborate on why this is bad? Surely sending an encoded password is better than a non-encoded one, and in a worst case only as bad as sending a cleartext password (i.e. what happens now).