From: Steve Dickson <steved@redhat.com>
To: Joe Doss <joe@solidadmin.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: wireguard.ko on RHEL8
Date: Thu, 28 Apr 2022 12:06:31 -0400 [thread overview]
Message-ID: <fde03ba9-d12a-e574-296f-747ad6141497@redhat.com> (raw)
In-Reply-To: <a18d6a8a-1dcc-3093-6931-5ffb1236d287@solidadmin.com>
Hey!
My apologies on my delayed response...
On 4/24/22 4:03 PM, Joe Doss wrote:
> Hey Steve,
>
> On 4/24/22 1:16 PM, Steve Dickson wrote:
>>
>> Trying to install wireguard.ko on a RHEL8 vm (4.18.0-348.el8.x86_64)
>> and I'm getting
>>
>> wireguard: module verification failed: signature and/or required
>> key missing - tainting kernel
>>
>> The entire error:
>> http://pastebin.test.redhat.com/1046896
>>
>> is there anything at can be done about that?
>>
>> I'm new to wireguard and I'm pretty impress...
>> It came up in both Fedora rawhide and an
>> unreleased verson of RHEL9...
>>
>> We are trying to used it as our network in
>> a community wide virtual NFS testing event
>> called Bakeathon [1]
>>
>> Again I'm new to wireguard but not to kernels ;-)
>> So if you could throw something at me to
>> help me get over this bum... It would be appreciated!
>>
>> Note: I am not member of this list so please
>> reply to be directly.
>
> You have secure boot enabled, so you need to generate a MOK key pair,
> manually sign your wireguard.ko, and enroll your MOK cert or disable
> secure boot.
>
> I use this script [1] to sign my NVIDIA drivers on my workstation after
> they are built via akmod.
>
> Hope this helps!
> Joe
>
> [1]: https://gist.github.com/jdoss/495e814ef4ef599e480c31d4843eb6c0
>
Thanks for the pointer... but I ended doing something
different that worked very well...
1) I enabled the Fedora Infra Cloud repo which has
the jdoss/wireguard repo
dnf copr enable jdoss/wireguard
2) Then installed the wireguard-dkms and wireguard-tools
packets which brought in the dkms command.
dnf install wireguard-dkms wireguard-tools
3) Then I simply reboot and mdks compile the module and
installed it... Very cool!
Thanks again!
steved.
prev parent reply other threads:[~2022-04-28 16:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-24 18:16 Steve Dickson
2022-04-24 20:03 ` Joe Doss
2022-04-28 16:06 ` Steve Dickson [this message]
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=fde03ba9-d12a-e574-296f-747ad6141497@redhat.com \
--to=steved@redhat.com \
--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).