very good suggestion! i've been following this thread with interest.
relevant to a commercial product i am working on. i thought keeping the
key in the address book was the most practical idea. but, you still
have to exchange the keys. the biggest problem is the lookup for a key
in a key server (keystore). but, automatically sending a separate
header sounds, er...automatic, transparent to the user. and lets the
system do the work. long, more than 10 digits, unintelligible email
addresses won't work. imho. can't be memorized, even if chunked. too
many pieces.
On 9/19/2014 4:31 AM, Werner Koch wrote:
On Fri, 19 Sep 2014 06:57, [email protected] said:
She can send you email at [email protected] once, and when your replies
all come from:
From: Derek Atkins <[email protected]>
then when she replies to you, she'll be sending encrypted emails. But
The same can be achieved with a separate mail header for the key and a
local association of key and mail address for future communication
(which you need for the above scheme also).
Shalom-Salam,
Werner
_______________________________________________
cryptography mailing list
[email protected]
http://lists.randombit.net/mailman/listinfo/cryptography
