So I was thinking about Jon's claim that keys should be 'disposable'. Not sure
if I buy that. But I did decide that key backup is a completely separate
problem and demands a separate infrastructure.
Let us imagine that I do the key-splitting and share in 5 places thing for my
Comcast email. I
On Aug 28, 2013, at 2:04 PM, Faré wrote:
> On Wed, Aug 28, 2013 at 4:15 PM, Phill wrote:
>> My target audience, like Perry's is people who simply can't cope with
>> anything more complex than an email address. For me secure mail has to look
>> feel and smell e
(This is the last week before school goes back which is stopping me getting to
the big iron and my coding platform if folk are wondering where the code is).
I had a discussion with some IETF types. Should I suggest a BOF in Vancouver?
Maybe this is an IRTF effort rather than IETF. One thing tha
On Aug 28, 2013, at 11:18 AM, Dave Horsfall wrote:
> On Wed, 28 Aug 2013, Perry E. Metzger wrote:
>
>> Anyway, I've already started implementing my proposed solution to that
>> part of the problem. There is still a need for a distributed database to
>> handle the lookup load, though, and one
My target audience, like Perry's is people who simply can't cope with anything
more complex than an email address. For me secure mail has to look feel and
smell exactly the same as current mail. The only difference being that sometime
the secure mailer will say 'I can't contact that person secur
On Aug 26, 2013, at 5:27 PM, The Doctor wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 08/26/2013 08:46 AM, Phillip Hallam-Baker wrote:
>
>> Which is why I think Ted Lemon's idea about using Facebook type
>> friending may be necessary.
>
> Or Gchat-style contacts.
>
>> I do
