[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110405163619.GA18727@openwall.com>
Date: Tue, 5 Apr 2011 20:36:19 +0400
From: Solar Designer <solar@...nwall.com>
To: oss-security@...ts.openwall.com
Subject: Re: Closed list
On Tue, Apr 05, 2011 at 09:46:25AM -0500, Tim Zingelman wrote:
> I'll also second the question someone else posed about how cc'ing
> others off the list could reasonably work if all messages are
> encrypted.
Messages from the list to members are always encrypted. Messages to the
list are preferably encrypted, but this is not enforced. (If a message
arrives to the list unencrypted, it is flagged as such in the encrypted
copies that are sent to members, so they're aware that the information
contained in the message is more likely to leak.)
So there are two ways to CC someone external:
1. Send the message to the list and to them unencrypted.
2. Send the message to both the list and the external address encrypted,
to their respective keys - e.g., GnuPG and Mutt support this just fine
(messages encrypted to more than one key).
The list currently does not propagate the To/CC headers to messages
arriving to members, though. Maybe this is something to improve such
that discussions CC'ing someone external can be maintained.
Alexander
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
