All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sommerseth <openvpn.list@...1114...>
To: Gert Doering <gert@...1296...>
Cc: openvpn-devel@lists.sourceforge.net
Subject: Re: [Openvpn-devel] [PATCH] Add topology in sample server configuration file
Date: Sat, 12 Jul 2014 12:41:14 +0200 (CEST)	[thread overview]
Message-ID: <63900614.19358.1405161674053.JavaMail.zimbra@...1795...> (raw)
In-Reply-To: <20140712094130.GM1118@...1296...>

----- Original Message -----
> From: "Gert Doering" <gert@...1296...>
> To: "David Sommerseth" <openvpn.list@...1114...>
> Cc: "Jan Just Keijser" <janjust@...1147...>, openvpn-devel@lists.sourceforge.net
> Sent: Saturday, 12 July, 2014 11:41:30 AM
> Subject: Re: [Openvpn-devel] [PATCH] Add topology in sample server configuration file
>
> > In addition, EL5 is the oldest distro we support (after we convinced James
> > to
> > ditch EL4 when that went officially EOL; not counting the extended support
> > some few customers may pay for).
> 
> Any way to convince RH to pick up this security-relevant fix?

I haven't had time to check the changelog for openssl on EL5 (not close to /my/ 
computers).  But it wouldn't surprise me if they have already fixed this.  But as
SSL_OP_NO_TICKET was introduced in a newer base release than EL5 uses, they have
most likely solved it in another way.  Maybe by always adding this flag implicit?
(Which would have the benefit of not needing to recompile all OpenSSL
applications with this flaw).

IIRC, the guy overseeing the Secure Response Team in RH is Mark Cox, which again
is also an upstream OpenSSL maintainer.  So I'm quite sure all RH releases have
fixed this issue.


--
kind regards,

David Sommerseth


  reply	other threads:[~2014-07-12 10:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11  8:00 [Openvpn-devel] [PATCH] Add topology in sample server configuration file Philipp Hagemeister
2014-07-11  8:51 ` Jan Just Keijser
2014-07-11  8:59   ` Arne Schwabe
2014-07-11  9:08     ` Jan Just Keijser
2014-07-11  9:22       ` Arne Schwabe
2014-07-11  9:33         ` Jan Just Keijser
2014-07-11 10:53           ` Arne Schwabe
2014-07-11 14:50             ` Jan Just Keijser
2014-07-11 18:07               ` Gert Doering
2014-07-11 18:17                 ` Jan Just Keijser
2014-07-11 18:35                   ` Steffan Karger
2014-07-11 23:17                     ` Jan Just Keijser
2014-07-12  9:08                       ` David Sommerseth
2014-07-12  9:41                         ` Gert Doering
2014-07-12 10:41                           ` David Sommerseth [this message]
2014-07-12 11:31                             ` Gert Doering
2014-07-12 12:55                               ` David Sommerseth
2014-07-12 13:50                                 ` Gert Doering
2014-07-13  9:31                                   ` [Openvpn-devel] more SSL_OP_NO_TICKET fallout Steffan Karger
2014-07-13 11:44                                     ` [Openvpn-devel] [PATCH applied] Re: Define dummy SSL_OP_NO_TICKET flag if not present in OpenSSL Gert Doering
2014-07-11 18:51                   ` [Openvpn-devel] [PATCH] Add topology in sample server configuration file Gert Doering
2014-07-11 11:05   ` Philipp Hagemeister
2014-07-11 12:35   ` Gert Doering
2014-07-11 14:54     ` Jan Just Keijser
2014-07-13 13:57 ` [Openvpn-devel] [PATCH applied] " Gert Doering

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=63900614.19358.1405161674053.JavaMail.zimbra@...1795... \
    --to=openvpn-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.