[cap-talk] Update on petname related anti-phishing work at the W3C
James A. Donald
jamesd at echeque.com
Sat Jun 30 18:40:21 EDT 2007
Tyler Close wrote:
> On 6/28/07, Jonathan S. Shapiro <shap at eros-os.com> wrote:
>> On Thu, 2007-06-28 at 12:45 -0700, Tyler Close wrote:
>>
>>> A password may still show up on screen when it is first created.
>>> Having a special editing mode for creating a password seems
>>> potentially confusing and awkward. Do people feel this step must also
>>> be more strongly protected from shoulder surfing?
>> DEFINITELY!
>>
>> Tyler:
>>
>> I'm *very* surprised that you have headed down the wrong trail so
>> completely where passwords are concerned.
>
> Are you saying you think the status quo for the login ceremony is
> superior to what I have proposed?
You are always going to get that reaction to any new proposal - that
what is done is the right way to do things, even though what is done is
manifestly not working.
Apply large quantities of salt.
>
>> It took *decades* to get
>> machines to finally blind passwords consistently, and it isn't a thing
>> to change lightly. Perhaps the working group really did give this change
>> adequate consideration, but that isn't apparent from the discussion that
>> has surfaced so far.
>
> Currently, the proposal is merely what I am proposing the Working
> Group should investigate over the coming months as a potential
> recommendation. So your criticism falls on me, rather than the Working
> Group as a whole.
Creating passwords blind creates serious problems with longer
passphrases, thus discouraging people from using long passphrases.
Most of the time, user knows he is not being shoulder surfed. Blind
entry should be an option - should have checkbutton that turns blind
entry on and off. Checkbutton should remember last state.
I recommend the user interface and behavior of Crypto Kong's "Create New
Password"
Create a secret passphrase to identify yourself
as <name> at <name>
Enter your secret passphrase
######## <entry field>
Confirm your secret passphrase by entering it a second time
######## <entry field>
# <checkbutton> Passphrase visible.
More information about the cap-talk
mailing list