[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: SSH revised

From: Marcus Brinkmann
Subject: Re: SSH revised
Date: Tue, 28 Mar 2006 22:58:32 +0200
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (Sanjō) APEL/10.6 Emacs/21.4 (i486-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Tue, 28 Mar 2006 22:05:50 +0200,
Bas Wijnen <address@hidden> wrote:
> On Tue, Mar 28, 2006 at 08:25:30PM +0200, Marcus Brinkmann wrote:
> > Anyway, I think user-based authentication would be severly crippled by
> > a confinement requirement.  One feature that would be useful is if
> > they can access arbitrary devices that are not supported by the
> > system, and for that alone you can forget about confinement here.
> Hmm, that makes sense.  So you suggest the user needs to select an ID first,
> after which an explicit confirmation is needed that it's the right one (for
> example showing the fingerprint picture)?

Yeah, well.  We need a user interface expert here.  If we are serious
about this, I would try to contact somebody like Ka-Ping Yee

Two confirmations make sense, but I was also considering an
"optimization": The "fingerprint picture" could be displayed as soon
as the user name is entered.  Then both could be confirmed at the same

I have a cuter name for the "fingerprint picture" already: The user's
mascot.  The pictures must be so cute that the user will log in just
to see the mascot :)

In principle, the mascot could be chosen by the user, as long as every
user has a distinguishable one.  That is a challenge for the
administrator, though, of course.  So, it would be an interesting
research field to automatically determine "distinguishability", or to
automatically generate many distinguishable mascots algorithmically.
Of course, there are many other possible policies to choose the
mascot, for example by using photos taken from the user (like on photo
id cards), or words from a lexicon, typeset in different fonts, colors
and sizes, ...

Of course, the whole issue is highly user-interface specific: For
accessibility reasons, you also need other solutions.  Audio files?
Quotes from the literature?  User data like residence address?  Lots
of possibilities here.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]