[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170624145714.GA30830@openwall.com>
Date: Sat, 24 Jun 2017 16:57:14 +0200
From: Solar Designer <solar@...nwall.com>
To: oss-security@...ts.openwall.com
Subject: Re: Qualys Security Advisory - The Stack Clash
On Wed, Jun 21, 2017 at 08:26:05PM -0400, Mike O'Connor wrote:
> In the past, I've proposed that the embargo mailing list archives
> themselves have an "embargo", after which they become public. That
> way, there's after-the-fact transparency, and it gives the folks who
> care a good idea of what happened. Is there anything sensitive at
> this point in, say, the March 2017 linux-distros archives??
There shouldn't be anything sensitive in old archives, such as in your
example. Technically, we can easily extract and make public the message
Subjects. For full messages, we need a way to mass-decrypt an mbox
containing PGP/MIME messages. Maybe I should list implementing a
program that would do that(*) as one of the options that a new distros
list member could choose as their contribution back to the community.
(*) Mutt hack maybe? Mutt processes those messages great, so having it
output them in decrypted form into another mbox and automatically loop
over all messages in the input mbox might do the trick.
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.
