> > For example if my turing return code setting is like this : > > ab"m"def (a > > fixed character "m" in position 3) > > > > Turing code Return code > > 123456 12m456 > > I get it. I like this idea for some situations (still won't fix the > challenge with creating multiple accounts though). If an account is > randomly assigned a position for the user to 'fix' that would also make > it so the user could not just pick a favorite position and character to > use for other accounts.
It's better to let the user choose. There is no problem in picking your favorite position and character, as long as it is not too obvious. There are many other simple algorithms, besides the "fix one character in predefined spot", which can be choosen. > > Of course I would forget all these things even if I had just a few > accounts. > - savings is a 4 in the 5th spot, > - company is a M in the 3rd spot, > - goddaughter's savings is a 5 in the 4th spot :) Why not use the same algorithm for each of your accounts? Choosing different algorithms does not necesarily make it more safe. As long as the main passphrases are different it will be ok. > > I think it is important to let the user supply a pgp key so that the > current settings can be safely emailed. Not necessary, you can just change it over the secure connection just like you can set a new passphrase. in your account settings. Danny http://two-cents-worth.com/?102468&EG --- You are currently subscribed to e-gold-list as: archive@jab.org To unsubscribe send a blank email to [EMAIL PROTECTED] Use e-gold's Secure Randomized Keyboard (SRK) when accessing your e-gold account(s) via the web and shopping cart interfaces to help thwart keystroke loggers and common viruses.
