11–16 of 16 posts
Earlier quoted context omitted.
Yeah. There's a Firesheep handler for news.yc too: https://github.com/codebutler/firesheep/wiki/Handlers This website should really be migrated to https.
Heaven forbid someone in a coffee shop posts something on your HN account…
I don't want to alarm anyone but so does this site. If your not using unique passwords for every site you use then you really should consider doing it. Tools such as 1Password make it ridiculously easy, there really is no excuse.
I don't want to alarm anyone but so does this site. If your not using unique passwords for every site you use then you really should consider doing it. Tools such as 1Password make it ridiculously easy, there really is no excuse.
Another way is to hash a "salt" password with the domain (or something site specific). So if my salt was "assword" and I put the last 4 characters from the domain name interspersed at the end of my password it would look like this: asswaotrodr. Giving you a unique and complicated password for every site.
Earlier quoted context omitted.
Another way is to hash a "salt" password with the domain (or something site specific). So if my salt was "assword" and I put the last 4 characters from the domain name interspersed at the end of my password it would look like this: asswaotrodr. Giving you a unique and complicated password for every site.
"Salting" it in that way doesn't increase your security by much? If they looked at your password, once they obtained it, how long would it take them to figure out what you were doing, and thereby be able to derive all your other passwords?
The suggested password strategy helps to protect against the later case.
Earlier quoted context omitted.
Yeah. There's a Firesheep handler for news.yc too: https://github.com/codebutler/firesheep/wiki/Handlers This website should really be migrated to https.
Heaven forbid someone in a coffee shop posts something on your HN account…