From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Christopher Bachner <hello@chrisbox.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: RHEL8 package install or build fail
Date: Fri, 28 Jun 2019 14:32:21 +0200 [thread overview]
Message-ID: <CAHmME9rNis62NiBZTyuaOjcxRtu2N9=90GaLR03_zQOPmYwFhg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rT11fPmBuRxa_sSRjW01ZN6eSJuDEpKOpGVbH2e=SZew@mail.gmail.com>
This commit fixes it and will be included in the next snapshot:
https://git.zx2c4.com/WireGuard/commit/?id=80f006d3656ce2858675020a23879e916ea8a4fc
[ec2-user@ip-172-31-24-82 ~]$ cat /etc/redhat-release
Red Hat Enterprise Linux release 8.0 (Ootpa)
[ec2-user@ip-172-31-24-82 ~]$ uname -a
Linux ip-172-31-24-82.eu-west-1.compute.internal
4.18.0-80.4.2.el8_0.x86_64 #1 SMP Fri Jun 14 13:20:24 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
[ec2-user@ip-172-31-24-82 ~]$ sudo ip link add wg0 type wireguard
[ec2-user@ip-172-31-24-82 ~]$ sudo wg
interface: wg0
[ec2-user@ip-172-31-24-82 ~]$ dmesg | grep wireguard
[ 693.365784] wireguard: loading out-of-tree module taints kernel.
[ 693.382433] wireguard: module verification failed: signature and/or
required key missing - tainting kernel
[ 693.390216] wireguard: WireGuard 0.0.20190601-8-g9e71cce-dirty
loaded. See www.wireguard.com for information.
[ 693.397561] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld
<Jason@zx2c4.com>. All Rights Reserved.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-06-28 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 13:18 RHEL8 package install or build fail Michael
2019-06-28 12:03 ` Jason A. Donenfeld
2019-06-28 12:05 ` Christopher Bachner
2019-06-28 12:07 ` Jason A. Donenfeld
2019-06-28 12:32 ` Jason A. Donenfeld [this message]
2019-06-28 14:41 ` Michael
2019-06-28 14:52 ` Jason A. Donenfeld
2019-07-02 19:51 ` Joe Doss
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='CAHmME9rNis62NiBZTyuaOjcxRtu2N9=90GaLR03_zQOPmYwFhg@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=hello@chrisbox.org \
--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).