From: Jeffrey Walton <noloader@gmail.com>
To: development@lists.ipfire.org
Subject: Re: Upgrading to OpenSSL 1.1.0
Date: Sat, 13 Jan 2018 07:30:22 -0500 [thread overview]
Message-ID: <CAH8yC8=5yXcM9yGt1sydGWKHmBj_d1ZzMY28Dh7z5hfZVtOMeg@mail.gmail.com> (raw)
In-Reply-To: <1515604119.2392.12.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
On Wed, Jan 10, 2018 at 12:08 PM, Michael Tremer
<michael.tremer(a)ipfire.org> wrote:
> ...
> So, again for me: What is the status of OpenVPN 2.4 now? I guess that
> should build with OpenSSL 1.1 out of the box.
I believe OpenSSL 1.1.0 is not supported by a few key packages, like
OpenVPN and OpenSSH.
Here is the OpenVPN bug:
https://community.openvpn.net/openvpn/ticket/759 . Here is the OpenSSH
bug: https://github.com/openssh/openssh-portable/pull/48 .
OpenVPN and OpenSSH are going to have to shit or get off the pot. TLS
1.3 is in final draft stages, and it will be adopted soon.
Jeff
next prev parent reply other threads:[~2018-01-13 12:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 13:12 Michael Tremer
2017-12-03 7:34 ` ummeegge
2017-12-07 11:21 ` ummeegge
2018-01-10 17:08 ` Michael Tremer
2018-01-12 11:02 ` ummeegge
2018-01-13 12:17 ` Michael Tremer
2018-01-14 10:59 ` ummeegge
2018-01-15 11:58 ` Michael Tremer
2018-01-16 11:36 ` ummeegge
2018-01-16 12:34 ` Jeffrey Walton
2018-01-16 13:02 ` Michael Tremer
2018-01-16 12:56 ` Michael Tremer
2018-01-16 14:28 ` Horace Michael
2018-01-18 10:07 ` ummeegge
2018-01-13 12:30 ` Jeffrey Walton [this message]
2018-01-15 11:59 ` Michael Tremer
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='CAH8yC8=5yXcM9yGt1sydGWKHmBj_d1ZzMY28Dh7z5hfZVtOMeg@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=development@lists.ipfire.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox