-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
NotDashEscaped: You need GnuPG to verify this message
Hi
On Thursday 17 April 2014 at 7:14:21 PM, in
, Ingo Klöcker wrote:
> Sure. One could do this. But I don't see the point of
> encrypting an individual copy for each To/Cc
> recipient. The o
On Thursday 17 April 2014 11:36:59 MFPA wrote:
> On Friday 11 April 2014 at 9:59:21 PM, in
> , Ingo Klöcker wrote:
> > Apart from using the '--throw-keyids' option you could
> > send multiple copies of the message. One copy for the
> > public recipients which is encrypted with the keys of
> > all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
NotDashEscaped: You need GnuPG to verify this message
Hi
On Friday 11 April 2014 at 9:59:21 PM, in
, Ingo Klöcker wrote:
> Apart from using the '--throw-keyids' option you could
> send multiple copies of the message. One copy for the
> public re
On Fri, 11 Apr 2014 22:59, kloec...@kde.org said:
> encrypted with the keys of all public recipients (To, Cc). And n copies
> for the n Bcc recipients where each copy is encrypted with the key of
> one Bcc recipient. That's what KMail does.
And that is the Right Thing to do. --throw-keyids or
On Thursday 10 April 2014 18:03:17 Nicolai Josuttis wrote:
> Can anybody answer/explain whether there is or might be a problem or
> risk if using encryption combined with bcc addresses with GPG?
> And if so, what should I do/avoid to run into this problem?
> I am especially interested in an answer
