From: Lucian Cristian <luci@createc.ro>
To: wireguard@lists.zx2c4.com
Subject: Re: Module verification failed
Date: Mon, 4 Sep 2017 23:54:03 +0300 [thread overview]
Message-ID: <242ba4db-a5f0-d13b-46f6-1246886d17d7@createc.ro> (raw)
In-Reply-To: <1504407150.3783820.1093515456.1E75D390@webmail.messagingengine.com>
[-- Attachment #1: Type: text/plain, Size: 1028 bytes --]
On 03.09.2017 05:52, DANG Fan wrote:
> I built WireGuard from source, and I got "Module verification failed"
> message when I tried to run "wg-quick up".
>
> Here is what I found in dmesg:
>
> [ 55.700967] wireguard: module verification failed: signature and/or
> required key missing - tainting kernel
> [ 55.701390] wireguard: WireGuard 0.0.20170810 loaded. See
> www.wireguard.com <http://www.wireguard.com> for information.
> [ 55.701391] wireguard: Copyright (C) 2015-2017 Jason A. Donenfeld
> <Jason@zx2c4.com <mailto:Jason@zx2c4.com>>. All Rights Reserved.
>
> ffs@server:~$ uname -a
> Linux server 4.4.0-93-generic #116-Ubuntu SMP Fri Aug 11 21:17:51 UTC
> 2017 x86_64 x86_64 x86_64 GNU/Linux
>
> Thanks!
>
>
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard
you have to add the driver to kernel sources and build the whole kernel
to not get this warning, is a new policy from kernel
Regards
[-- Attachment #2: Type: text/html, Size: 2134 bytes --]
next prev parent reply other threads:[~2017-09-04 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 2:52 DANG Fan
2017-09-04 20:54 ` Lucian Cristian [this message]
2017-09-04 20:57 ` Jason A. Donenfeld
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=242ba4db-a5f0-d13b-46f6-1246886d17d7@createc.ro \
--to=luci@createc.ro \
--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).