On Mon, Feb 28, 2005 at 06:40:22PM +0100, Joost van Baal wrote:
>
> I will write and publish a patch which integrates PGP signature
> validation and re-encryption of encrypted posts to mailman. Specs are:
>
> - A post will be distributed only if the PGP signature on the post is from
> one of t
On Wed, 2 Mar 2005 12:37:41 +0100
Brad Knowles <[EMAIL PROTECTED]> wrote:
> True. A session key would be encrypted to each key id, so the key ids
> would be visible. However, subscriber information is not too hard to
> get from Mailman even when it's supposedly limited to being available
> only
Brad Knowles wrote:
Further, this will reveal
all recipients' key ids - something not wanted in anonymous lists.
True. A session key would be encrypted to each key id, so the key
ids would be visible. However, subscriber information is not too
On Wed, 2005-03-02 at 13:28 +0100, Stefan Schlott wrote:
> Nigel Metheringham wrote:
>
> > In theory, you could encrypt the message once with a session key, and
> > then distribute it n times, each time adding the packet which has the
> > session key encrypted with the public key of the recipient.
Nigel Metheringham wrote:
In theory, you could encrypt the message once with a session key, and
then distribute it n times, each time adding the packet which has the
session key encrypted with the public key of the recipient.
...which is the very thing making gpg encryption so slow :-)
The expensi
On Wed, 2005-03-02 at 12:37 +0100, Brad Knowles wrote:
> At 8:31 AM +0100 2005-03-02, Stefan Schlott wrote:
> >Further, this will reveal
> > all recipients' key ids - something not wanted in anonymous lists.
>
> True. A session key would be e
At 8:31 AM +0100 2005-03-02, Stefan Schlott wrote:
This will create huge messages in large MLs.
Each additional recipient would be a few extra bytes in the
encrypted message. However, since the message is compressed first,
unless you've got a list of thousands and thousands of recipients,
the
Hi,
Stefan: thanks a lot for publishing your patch! Of course, this is
_very_ helpful!
Great to hear that :-)
This will create huge messages in large MLs. Further, this will reveal
all recipients' key ids - something not wanted in anonymous lists.
Imho the tradeoff lies somewhere inbetween - enc
Hi,
Stefan: thanks a lot for publishing your patch! Of course, this is
_very_ helpful!
On Wed, Mar 02, 2005 at 08:31:56AM +0100, Stefan Schlott wrote:
> >> I didn't figure out at
> >> first glance how chunking works... otherwise, a mail might be encr
Hi,
Have either of you solved the problem of Mailman not preserving
white space in the message body? This kind of thing is death to
messages signed or encrypted with PGP, and I have yet to hear of anyone
who has addressed this issue.
As already mentioned, I didn't cover the sign-only case;
At 9:01 PM +0100 2005-03-01, Stefan Schlott wrote:
I will write and publish a patch which integrates PGP signature
validation and re-encryption of encrypted posts to mailman. Specs are:
Don't duplicate work which has already been done :-) I made
modifications to mailman 2.1.5 for encrypted ma
Hi Joost,
I will write and publish a patch which integrates PGP signature
validation and re-encryption of encrypted posts to mailman. Specs are:
Don't duplicate work which has already been done :-) I made
modifications to mailman 2.1.5 for encrypted mailinglists, but I kept
quiet for testing. T
Hi,
I will write and publish a patch which integrates PGP signature
validation and re-encryption of encrypted posts to mailman. Specs are:
- A post will be distributed only if the PGP signature on the post is from
one of the list members.
- For sending encrypted email, a list member encrypts t
13 matches
Mail list logo
