This is a multi-part message in MIME format.
--===============1368298984==
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0024_01C3E34E.4F303720"
This is a multi-part message in MIME format.
------=_NextPart_000_0024_01C3E34E.4F303720
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: 7bit
I did a study trying to find out what problems undergraduate information
management and computer science students had with passwords, by beefing
up the system logs to record all password submissions on a web-based
examination ap and then me interpreting them without help from the
people who made the mistake (ie. I could have categorised them wrong).
Here's what I say I found: about 15 percent of password problems (when a
password submitted at a password prompt is incorrect) are typing
related. The vast bulk of errors were to do with having too many
passwords - see below. So, the proposed solutions could help a bit, but
won't tackle the main problem.
Problem type
Proportion
Description of problem
Expired Pwd
37%
Using an expired password instead of the currently valid one.
Substitution
15%
Using some password like sequence of characters instead of the
currently valid password.
Enter
9%
Pressing Enter before typing a password - no password was entered
in the login attempt
Omission
6%
Omitting a necessary character from an otherwise correct password
Addition
5%
Having an unnecessary character in an otherwise correct password
Partial Recall
5%
Recalling part of a password, but not the rest of it
Distribution
4%
A problem occurred during the initial distribution of the account
details
System Error
3%
A malfunction in the password mechanism
Replacement
2%
Having incorrect characters in an otherwise correct password
Blend
1%
Mixing parts of passwords together
Capitalisation
1%
Using the wrong capitalisation in all or part of a password
Userid
1%
Entering the username instead of the password
Sacha
> -----Original Message-----
> From: bj@altern.org [mailto:bj@altern.org]
> Sent: 19 January 2004 00:45
> To: kde-usability@kde.org
> Subject: Allowing No Hide mode in passwords
>
>
> Hello !
>
> First post to this list :-). As maintainer of KGpg, a user
> told me he was
> using long passwords, and that it was hard to tell if he made
> a mistake
> because currently KPasswordDialog only displays
> ************** when you type
> a password. He would like to be able to actually see the
> password he is
> typing.
>
> I think this could be a usability enhancement (for example
> for people that
> have problem with typing)
>
------=_NextPart_000_0024_01C3E34E.4F303720
Content-Type: text/html;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
I did a study trying to find out what =
problems=20
undergraduate information management and computer science students had =
with=20
passwords, by beefing up the system logs to record all password =
submissions on a=20
web-based examination ap and then me interpreting them without help from =
the=20
people who made the mistake (ie. I could have categorised them =
wrong). =20
Here's what I say I found: about 15 percent of password problems (when =
a password=20
submitted at a password prompt is incorrect) are typing related. =
The vast=20
bulk of errors were to do with having too many passwords - see=20
below. So, the proposed solutions could help =
a bit,=20
but won't tackle the main problem.
Problem=20
type
Proportion
Description of=20
problem
Expired =20
Pwd
37%
Using an =
expired password=20
instead of the currently valid one.
Substitution
15%
Using some =
password like=20
sequence of characters instead of the currently valid=20
password.
Enter
9%
Pressing Enter =
before=20
typing a password – no password was entered in the login=20
attempt
Omission
6%
Omitting a =
necessary=20
character from an otherwise correct =
password
Addition
5%
Having an =
unnecessary=20
character in an otherwise correct =
password
Partial=20
Recall
5%
Recalling part =
of a=20
password, but not the rest of it
Distribution
4%
A=20
problem occurred during the initial distribution of the account=20
details
System=20
Error
3%
A=20
malfunction in the password mechanism
Replacement
2%
Having =
incorrect=20
characters in an otherwise correct =
password
Blend
1%
Mixing parts of =
passwords=20
together
Capitalisation
1%
Using the wrong =
capitalisation in all or part of a =
password
Userid
1%
Entering the =
username=20
instead of the =
password
Sacha
>=20
-----Original Message-----
> From: bj@altern.org [mailto:bj@altern.org]
> Sent: 19 =
January 2004=20
00:45
> To: kde-usability@kde.org
> Subject: Allowing No =
Hide mode=20
in passwords
>
>
> Hello !
>
> First post =
to this=20
list :-). As maintainer of KGpg, a user
> told me he was
> =
using=20
long passwords, and that it was hard to tell if he made
> a=20
mistake
> because currently KPasswordDialog only displays
>=20
************** when you type
> a password. He would like to be =
able to=20
actually see the
> password he is
> typing.
>
> =
I think=20
this could be a usability enhancement (for example
> for people=20
that
> have problem with typing)
>
------=_NextPart_000_0024_01C3E34E.4F303720--
--===============1368298984==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability
--===============1368298984==--