[147126] in cryptography@c2.net mail archive

home help back first fref pref prev next nref lref last post

[Cryptography] Key management,

daemon@ATHENA.MIT.EDU (Perry E. Metzger)
Sat Sep 14 16:22:55 2013

X-Original-To: cryptography@metzdowd.com
Date: Sat, 14 Sep 2013 12:46:20 -0400
From: "Perry E. Metzger" <perry@piermont.com>
To: Max Kington <mkington@webhanger.com>
In-Reply-To: <CAMOP+b76tdPp-T7Zrw89t1w5UEwh9HVwa4tzSD0VjMpbNjK9Ow@mail.gmail.com>
Cc: "cryptography@metzdowd.com List" <cryptography@metzdowd.com>
Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com

On Sat, 14 Sep 2013 17:23:40 +0100 Max Kington
<mkington@webhanger.com> wrote:
> The keys. This to me is the critical point for widespread adoption,
> key management. How do you do this in a way that doesn't put people
> off immediately.

You don't seem to be entirely talking about key management, given
that you talk about mailpile and parley. Parley seems to be simply
talking about *key storage* for example, which is a different kettle
of fish.

However, on the topic of key management itself, my own proposal was
described here:

http://www.metzdowd.com/pipermail/cryptography/2013-August/016870.html

In summary, I proposed a way you can map IDs to keys through pure
long term observation/widely witnessed events. The idea is not
original given that to some extent things like Certificate
Transparency already do this in other domains.


Perry
-- 
Perry E. Metzger		perry@piermont.com
_______________________________________________
The cryptography mailing list
cryptography@metzdowd.com
http://www.metzdowd.com/mailman/listinfo/cryptography

home help back first fref pref prev next nref lref last post