News for hackers. Stuff that matters.

aadamov

Re:When to join a startup on Saturday January 23, 2016 @01:06PM (#10959243)
Spot on our trajectory for the last two years
Re:On the Fetishism of Capital and Prestige on Saturday April 27, 2013 @04:06PM (#5618888)
High on emotions. Low on facts and ideas.
Re:Evernote hacked on Saturday March 02, 2013 @04:08PM (#5311041)
Indeed, the assumption is that attacker has limited window of opportunity to grab the data. Taking that as a base assumption, it would make sense two store parts of the hashed password in two separate databases on two separate machines. Hacker would have to gain access to both. My initial alternative was to add some trick inside of the code, like a simple shuffling of characters. Assuming that code is not stored on the same machine as DB that should increase security considerably. But either concept would work. Of course it does not remove the need for higher degree of difficulty for hashing itself.
Re:Evernote hacked on Saturday March 02, 2013 @01:02PM (#5310321)
But this is why we do one or both things: strip obvious things from hashed password and store them separately or add a trivial character reshuffling algorithm. The point is that hacker would not only have to steal your hashed passwords, but also steal and understand your code. Makes it more complicated.