wireguard.ko on RHEL8

Hello, 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

Re: wireguard.ko on RHEL8

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/10468

[PATCH 0/1] wg syncconf not clearing PresharedKey/PersistentKeepalive

Hi, I noticed that wg syncconf does not actually clear PresharedKey and PersistentKeepalive values if those are not set in the file but set in the running config. The proposed patch changes that to always clear those if they are not set in the configuration file, which imho is the correct behavior

[PATCH 1/1] wg syncconf: explicitly reset PresharedKey/PersistentKeepalive

make wg syncconf correctly clear a preshared key or keepalive in case the file config does not define those; currently syncconf does not change these settings at all if runtime has them set but file does not --- src/setconf.c | 8 1 file changed, 8 insertions(+) diff --git a/src/setconf.

[PATCH] [wireguard-go] Pool for endpoint objects

Use sync.pool for endpoints to avoid memory allocations on each receive. When an endpoint is returned in bind linux, go allocates memory on the heap By using sync.pool, the allocations can be reused, and can dramatically be more efficient. This patch includes the changes for linux bind, and an opt

[PATCH] Fix Wireguard-Apple Logger Memory Leak (Fix Wireguard-Apple Logger Memory Leak)

Using "Instruments" tool shows every log message from the SystemExtension creates a persistent allocation. Although it seems there is no retain cycle, the allocated resources are not freed, which might be caused by the way the function is invoked using golang instead of the usual swift invocation f

Re: Using WireGuard on Windows as non-admin - proper solution?

Hi, On Sun, Nov 29, 2020 at 9:59 PM Jason A. Donenfeld wrote: On Sun, Nov 29, 2020 at 8:44 PM Phillip McMahon wrote: Won't drag this already long and confusing thread out. Not challenging the current implementation, just the notion that any other suggestion is a dead end and the topic is close