Hi list,
Le 17/06/2020 à 19:53, Jason A. Donenfeld a écrit :
> Hmm, still not able to reproduce.
>
> Are you sure you're running the latest up to date module? Try
> uninstalling kmod-wireguard and reinstalling?
>
> What driver is your ethernet NIC using?
>
For what it's worth, I seem to have t
On Thu, Jun 18, 2020 at 10:48 AM Jean-Denis Girard wrote:
> [ 17.886512] wireguard: WireGuard 1.0.20200520 loaded. See
> www.wireguard.com for information.
20200520 is old. Have you tried the newer version yet?
On Thu, Jun 18, 2020 at 10:48 AM Jean-Denis Girard wrote:
> For what it's worth, I seem to have the same problem on a CentOS-7
> virtual machine hosted on VMware with vmxnet3. It has been working fine
> since installed in 2017, but does lock up after upgrading to
> kernel-3.10.0-1127.8.2.el7.x86_6
On 6/16/20 9:53 PM, Joe Perches wrote:
> On Mon, 2020-06-15 at 21:57 -0400, Waiman Long wrote:
>> v4:
>> - Break out the memzero_explicit() change as suggested by Dan Carpenter
>> so that it can be backported to stable.
>> - Drop the "crypto: Remove unnecessary memzero_explicit()" patch
I'm looking for a nice way to rotate keypairs with Wireguard. How much time
do you have to update the initiator and responder with new keypairs before
handshakes fail?
If I understood the whitepaper correctly, sessions aren't immediately invalid
when you change a peers identity. Instead, you have
Thanks for your comments!
I really like the systemctl reload approach. My main intention with
this patchset was to add this feature to wg-quicks arsenal because (at
least for me) it's the most obvious approach. I mainly use `wg-quick
down wg0 && wg0 up wg0`, I think you guys see where I'm coming fr
Hi again, Jason,
[Adding a bit of extra context for linux-arm-kernel.]
On Wed, 17 Jun 2020 at 22:02, Jason A. Donenfeld wrote:
>
> But I am wondering: has anybody heard about toolchain progress toward
> fixing this? Couldn't the compiler reorder functions itself more
> intelligently? Or avoid em
On 18/06/2020 05:31, dx...@xirihosting.com wrote:
6) Yum operations trigger a lot of exclutions for elrepo, but nothing seems
wireguard related:
Not related to this bug, so for information only. The following is
caused by a difference in the way CentOS compose their repositories over
RHEL:
Le 18/06/2020 à 09:48, Jason A. Donenfeld a écrit :
> I am unable to reproduce this issue with vmxnet3. However, as I noted
> earlier, your wireguard version seems old. Try updating everything at
> once, and then see.
yum updated to wireguard-dkms.noarch 1:1.0.20200611-1.el7
By the way, yum compl
On Thu, Jun 18, 2020 at 2:10 PM Jean-Denis Girard wrote:
>
> Le 18/06/2020 à 09:48, Jason A. Donenfeld a écrit :
> > I am unable to reproduce this issue with vmxnet3. However, as I noted
> > earlier, your wireguard version seems old. Try updating everything at
> > once, and then see.
>
> yum updat
Hey Rui,
I fixed it! It turned out to be caused by -fvisibility=hidden undoing
the effect of the binutils fix from a while back. Here's the patch
that makes the problem go away:
https://git.zx2c4.com/wireguard-linux-compat/commit/?id=178cdfffb99f2fd6fb4a5bfd2f9319461d93f53b
This will be in the n
Looks as though in the end this is a binutils bug with
-fvisibility=hidden. Details on
https://sourceware.org/bugzilla/show_bug.cgi?id=12532#c9
12 matches
Mail list logo
