[154005] in North American Network Operators' Group
Re: How to fix authentication (was LinkedIn)
daemon@ATHENA.MIT.EDU (Kyle Creyts)
Wed Jun 20 19:32:19 2012
In-Reply-To: <32087489.10264.1340234805345.JavaMail.root@benjamin.baylink.com>
Date: Wed, 20 Jun 2012 19:31:40 -0400
From: Kyle Creyts <kyle.creyts@gmail.com>
To: Jay Ashworth <jra@baylink.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Guess we all need implants deep in less-than-easily-operable areas to
bind us to a digitally-accessible identity. This would make for an
interesting set of user-based trust-anchoring paradigms, at least.
On Wed, Jun 20, 2012 at 7:26 PM, Jay Ashworth <jra@baylink.com> wrote:
> ----- Original Message -----
>> From: "Leo Bicknell" <bicknell@ufp.org>
>
>> SSL certificates could be used this way today.
>>
>> SSH keys could be used this way today.
>>
>> PGP keys could be used this way today.
>>
>> What's missing? A pretty UI for the users. Apple, Mozilla, W3C,
>> Microsoft IE developers and so on need to get their butts in gear
>> and make a pretty UI to create personal key material, send the
>> public key as part of a sign up form, import a key, and so on.
>
> Yes, but you're securing the account to the *client PC* there, not to
> the human being; making that Portable Enough for people who use and
> borrow multiple machines is nontrivial.
>
> Cheers,
> -- jra
> --
> Jay R. Ashworth =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Baylink =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 jra@baylink.com
> Designer =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 The Things I Think =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 RFC 2100
> Ashworth & Associates =A0 =A0 http://baylink.pitas.com =A0 =A0 =A0 =A0 20=
00 Land Rover DII
> St Petersburg FL USA =A0 =A0 =A0http://photo.imageinc.us =A0 =A0 =A0 =A0 =
=A0 =A0 +1 727 647 1274
>
--=20
Kyle Creyts
Information Assurance Professional
BSidesDetroit Organizer
