[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKTMEKMadJcmiY-ar=6S3OLXysKcFu=vcrC-xytXCai7MecDjQ@mail.gmail.com>
Date: Tue, 14 Oct 2014 23:32:20 -0700
From: Krassimir Tzvetanov <maillists@...ssi.biz>
To: oss-security@...ts.openwall.com
Subject: Re: Truly scary SSL 3.0 vuln to be revealed soon:
If I have to complain about something (and this is a general concern not
poodle-centric) it would be that I will be good to get heads up on
vulnerable versions.
Even if no details are released at that time it would be good to have 4
hours heads up. In most circumstances this is not sufficient time to
reverse and start exploiting but would allow responders to enumerate the
products/systems affected and contact the owners.
In a production environment this might mean cancelling planned change
requests and in development environments this might mean preparing the
necessary engineering teams and test environments.
In some cases this will also make it easy for people from other time zones
to have the proper incident managers engaged (provided they have less
senior stuff or automation monitoring this list).
So if you are working with embargoed info consider encouraging the owners
to disclose affected versions prior to the full report.
Best,
Krassimir
On Tue, Oct 14, 2014 at 11:13 PM, mancha <mancha1@...o.com> wrote:
> On Wed, Oct 15, 2014 at 05:28:34AM +0000, Sona Sarmadi wrote:
>
> Hanno was sharing already-public information.
>
> Adam Langley tweeted it at Tue Oct 14 22:28:32 UTC 2014 [1] and Hanno
> emailed the news to oss-sec 12 minutes and change later. I didn't check
> to see if there were even earlier public disclosures than agl's.
>
> Someone is owed an apology.
>
> --mancha
>
> [1] https://twitter.com/agl__/status/522151998502617088
>
> PS Ugh, top-posting.
>
> > Thanks Hanno,
> >
> > A reflection: Maybe we shouldn't post information like this here or
> > somewhere else which is not published yet even if the information has
> > leak out? Although all members here are reliable but it is still an
> > open mailing list and we should be careful and act more responsible.
> >
> > Cheers Sona
> >
> > > It's out:
> > >
> > > https://www.openssl.org/~bodo/ssl-poodle.pdf
> > > http://googleonlinesecurity.blogspot.de/2014/10/this-poodle-bites-
> > > exploiting-ssl-30.html
> > >
> > > My conclusion stays the same: Disable SSLv3.
> > >
> > > -- Hanno Böck http://hboeck.de/
> > >
> > > mail/jabber: hanno@...eck.de GPG: BBB51E42
>
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.
