Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

While not entirely random, would a "date based" salt work as well? Say, the date that the entry was added? This would still negate rainbow tables as a specific user entry needs to be targeted.


It would probably work well enough, but... why not just add a proper random salt field that isn't tied to anything an attacker could guess? Is something like 8 bytes per user too expensive?


Perhaps I'm missing something but... wouldn't you still need to store the random salt field somewhere in the database?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: