Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: elrepo@lists.elrepo.org
Cc: Joe Doss <joe@solidadmin.com>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: More reliable packages available for RHEL, CentOS, and Fedora
Date: Sat, 4 Apr 2020 15:22:18 -0600	[thread overview]
Message-ID: <CAHmME9qr+PHsn6EJAwhkdu0NwN3g3zdkJfX5X+aBjwovN9grsg@mail.gmail.com> (raw)
In-Reply-To: <20200404211246.GA10066@zx2c4.com>

I was asked to loop in the ELRepo mailing list too. Below is the email
I just sent out to wgml.

On Sat, Apr 4, 2020 at 3:12 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hey folks,
>
> Joe Doss (cc'd) has maintained our DKMS packages for Fedora, RHEL, and CentOS
> for the last several years on his copr. Recently there have been some nice
> changes due to the 1.0ing of WireGuard.
>
> - Fedora 32 will get Linux 5.6, so it won't need the DKMS package:
>   https://bodhi.fedoraproject.org/updates/FEDORA-2020-e8b6474ee5
> - Fedora 31 and 30 will also get Linux 5.6 during the next month, so
>   they won't need the DKMS package.
> - Joe has joined ELRepo (cc'd) as a package maintainer, so RHEL/CentOS
>   7/8 will now have binary kmods built over there, signed with ELrepo's
>   validating UEFI Secure Boot key, so enterprise users will have more
>   reliable updates.
> - I've contacted Red Hat about bringing WireGuard directly into the RHEL kernel;
>   we'll see what happens there. (I've also reached out to Oracle
>   regarding their enterprise situation.)
> - The wireguard-tools package moved into Fedora-proper, which means it's
>   now available on F32, F31, F30, and RHEL/CentOS 7,8 via EPEL.
>
> The net result of this is that when F31 and F32 move to 5.6, we will no
> longer need the copr with DKMS, at all, and also that today, enterprise
> users now have a more reliable way to use WireGuard.
>
> The most up to date instructions are on https://www.wireguard.com/install/
> but the current situation is:
>
> Fedora 32 now and Fedora 31,30 in a few weeks from now:
> $ sudo dnf install wireguard-tools
>
> Fedora 31,30 now, but not in a few weeks from now:
> $ sudo dnf copr enable jdoss/wireguard
> $ sudo dnf install wireguard-dkms wireguard-tools
>
> RHEL 8:
> $ sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
> $ sudo yum install https://www.elrepo.org/elrepo-release-8.el8.elrepo.noarch.rpm
> $ sudo yum install kmod-wireguard wireguard-tools
>
> CentOS 8:
> $ sudo yum install elrepo-release epel-release
> $ sudo yum install kmod-wireguard wireguard-tools
>
> RHEL 7:
> $ sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
> $ sudo yum install https://www.elrepo.org/elrepo-release-7.el7.elrepo.noarch.rpm
> $ sudo yum install kmod-wireguard wireguard-tools
>
> CentOS 7:
> $ sudo yum install epel-release
> $ sudo yum install https://www.elrepo.org/elrepo-release-7.el7.elrepo.noarch.rpm
> $ sudo yum install kmod-wireguard wireguard-tools
>
> Thanks,
> Jason

  reply	other threads:[~2020-04-04 21:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 21:12 Jason A. Donenfeld
2020-04-04 21:22 ` Jason A. Donenfeld [this message]
2020-04-15 21:41 ` Jason A. Donenfeld
2020-04-15 21:47   ` Eddie

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=CAHmME9qr+PHsn6EJAwhkdu0NwN3g3zdkJfX5X+aBjwovN9grsg@mail.gmail.com \
    --to=jason@zx2c4.com \
    --cc=elrepo@lists.elrepo.org \
    --cc=joe@solidadmin.com \
    --cc=wireguard@lists.zx2c4.com \
    /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;
as well as URLs for NNTP newsgroup(s).