Timeline for Hashing a password before using for online accounts
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 17, 2017 at 13:14 | history | edited | CommunityBot |
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
|
|
| Jan 25, 2016 at 12:18 | comment | added | Matty | @Iam Nick, you can choose yourself whether or not you want to include the 'http' and 'www' in the site's name. They suggests omitting all of that and sticking to just 'stackoverflow.com' (for example). | |
| Jan 25, 2016 at 11:35 | comment | added | Agent_L | passwordmaker.org is another one. Complete with javascript implementation so you can examine it yourself. | |
| Jan 25, 2016 at 8:13 | comment | added | Iam Nick | This App has a few flaws, such as taking a version of the URL, where "/", "www.", "http://" and "https://" would all be accounted for when they'd do well to be ignored. However a real plus side to this approach nobody seems to have mentioned is the plausible deniability, because no usernames or other info are stored! This was my main reason for creating an app like this. | |
| Jan 24, 2016 at 14:05 | history | answered | Matty | CC BY-SA 3.0 |