Re: [Mutt] #2992: Re: wish: enable encrytion to arbitrary number of
#2992: Re: wish: enable encrytion to arbitrary number of keys (was: Re:
Comment (by Mutt):
{{{
#2992: Re: wish: enable encrytion to arbitrary number of keys (was: Re:
Comment (by Mutt):
{{{
#2992: Re: wish: enable encrytion to arbitrary number of keys (was: Re:
Changes (by brendan):
* priority: major => minor
* type: defect => enhancement
* component: mutt => crypto
* milestone: => 2.0
Old description:
> {{{
> On Fri, Nov 23, 2007 at 03:34:54AM -0500, Derek Martin wrote:
>
> > While I don't really oppose this, it seems to me that the far saner
> > way to deal with this is for the mailing list software to allow the
> > subscribing users to upload their public key, and to make the mailing
>
> It would make it easier in some cases, but you do lose security -
anybody
> who can somehow get themselves onto the list can read it, and anybody
> compromising the mailing list host automatically gets to read
everything.
> If
> the senders do the encryption, that doesn't happen.
>
> Whether most people need that level of security is another question,
but
> then again most people don't use encrypted mailing lists at all... :-)
> }}}
New description:
On Fri, Nov 23, 2007 at 03:34:54AM -0500, Derek Martin wrote:
> While I don't really oppose this, it seems to me that the far saner
> way to deal with this is for the mailing list software to allow the
> subscribing users to upload their public key, and to make the mailing
It would make it easier in some cases, but you do lose security -
anybody
who can somehow get themselves onto the list can read it, and anybody
compromising the mailing list host automatically gets to read
everything.
If
the senders do the encryption, that doesn't happen.
Whether most people need that level of security is another question, but
then again most people don't use encrypted mailing lists at all... :-)
}}}
}}}
--
Ticket URL: <http://dev.mutt.org/trac/ticket/2992#comment:>