[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141015055844.GA2572@gremlin.ru>
Date: Wed, 15 Oct 2014 09:58:44 +0400
From: gremlin@...mlin.ru
To: oss-security@...ts.openwall.com
Subject: Re: SSL POODLE (Truly scary SSL 3.0 vuln)
On 15-Oct-2014 05:28:34 +0000, Sona Sarmadi wrote:
> 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.
Why? Old ciphers are well known as totally insecure (generally
speaking, even some "new" are insecure as well), so the POODLE
description does nothing but shows one more attack vector.
The protection against the POODLE is quite simple:
1. For servers: disable weak encryption (in assumption they are
updated on a regular basis).
2. For users: update old software. Alas, fully disabling weak
encryption (e.g. set security.tls.version.min == 3 in Firefox)
isn't what we can demand, but that leaves the user personally
responsible for any and all data leaks.
>> It's out:
TP detected...
--
Alexey V. Vissarionov aka Gremlin from Kremlin <gremlin ПРИ gremlin ТЧК ru>
GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
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.
