On Tue, 18 Dec 2012 23:30:30 +0100, clay <[email protected]> wrote:
Every recommendation is a system based on some secure server storing passwords. How about hash systems? I use http://passwordmaker.org/ You only need to remember one password, the hash system generates new passwords for every new site, and there is no server-storage involved. Nothing to hack, protect, or lose access to.
I didn't know passwordmaker and I'll have a deeper look at it in the next days. In the past I've thought of a similar approach, but with some doubts:
1. In case one password is compromised (e.g. by eavesdropping) you have to change the password and give up with this approach, at least for the compromised site. 2. Sometimes the URL might change. For instance, one of my banks introduced a redesigned website. The original URL was www.bank.it, for some time it redirected to new.bank.it (transitory period in which the original website was still available). This would have caused at least some annoyance (forced to change the password) at least temporarily.
Still, it is of some interest. -- Fabrizio Giudici - Java Architect @ Tidalwave s.a.s. "We make Java work. Everywhere." http://tidalwave.it/fabrizio/blog - [email protected] -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
