Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-03-09 Thread Celejar
On Mon, 09 Mar 2020 17:22:57 -0400 Daniel Kahn Gillmor wrote: > On Mon 2020-02-03 13:20:22 -0500, Celejar wrote: > > Okay, now I've gotten it. I've uninstalled nftables and put in the > > debug line, and I get this (with 1.0.20200121-2): > > > > ~# ifdown wg0 > > [#] ip -4 rule delete table

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-03-09 Thread Daniel Kahn Gillmor
On Mon 2020-02-03 13:20:22 -0500, Celejar wrote: > Okay, now I've gotten it. I've uninstalled nftables and put in the > debug line, and I get this (with 1.0.20200121-2): > > ~# ifdown wg0 > [#] ip -4 rule delete table 51820 > [#] ip -4 rule delete table main suppress_prefixlength 0 > [#] ip link

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-02-03 Thread Celejar
On Tue, 28 Jan 2020 14:14:01 -0500 Daniel Kahn Gillmor wrote: > On Mon 2020-01-27 19:45:36 -0500, Celejar wrote: > > I think I'm probably missing something, but lately "ifdown wg0" isn't > > segfaulting (even after downgrading back to 1.0.20200102-1) - but it > > doesn't seem to be calling

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-01-28 Thread Daniel Kahn Gillmor
On Mon 2020-01-27 19:45:36 -0500, Celejar wrote: > I think I'm probably missing something, but lately "ifdown wg0" isn't > segfaulting (even after downgrading back to 1.0.20200102-1) - but it > doesn't seem to be calling iptables-restore at all, but only nft: Ah, that'd be because you installed

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-01-27 Thread Celejar
On Thu, 23 Jan 2020 12:16:07 -0500 Daniel Kahn Gillmor wrote: > On Thu 2020-01-23 00:01:57 -0500, Celejar wrote: > > So right after my last email, I upgraded to 1.0.20200121-1, and now I > > no longer get a segfault. Is there anything further I should do? Should > > I do a downgrade and try your

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-01-23 Thread Daniel Kahn Gillmor
On Thu 2020-01-23 00:01:57 -0500, Celejar wrote: > So right after my last email, I upgraded to 1.0.20200121-1, and now I > no longer get a segfault. Is there anything further I should do? Should > I do a downgrade and try your modification? If you don't mind downgrading (just the wireguard-tools

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-01-22 Thread Celejar
On Wed, 22 Jan 2020 16:47:17 -0500 Daniel Kahn Gillmor wrote: > Control: tags 946996 + moreinfo > > On Tue 2020-01-21 22:18:45 -0500, Celejar wrote: > > Sorry, I'm still getting it: > > > > ~# apt-cache policy wireguard-tools > > wireguard-tools: > > Installed: 1.0.20200102-1 > >

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-01-22 Thread Daniel Kahn Gillmor
Control: tags 946996 + moreinfo On Tue 2020-01-21 22:18:45 -0500, Celejar wrote: > Sorry, I'm still getting it: > > ~# apt-cache policy wireguard-tools > wireguard-tools: > Installed: 1.0.20200102-1 > Candidate: 1.0.20200102-1 > Version table: > *** 1.0.20200102-1 500 > 500

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-01-21 Thread Celejar
On Tue, 21 Jan 2020 10:36:25 -0500 Daniel Kahn Gillmor wrote: > Control: reassign 946996 iptables > Control: affects 946996 + wireguard-tools > > Hi Celejar-- > > On Thu 2019-12-19 00:00:39 -0500, Celejar wrote: > > Package: wireguard-tools > > Version: 0.0.20191212-1 > > Severity: normal > >

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2020-01-21 Thread Daniel Kahn Gillmor
Control: reassign 946996 iptables Control: affects 946996 + wireguard-tools Hi Celejar-- On Thu 2019-12-19 00:00:39 -0500, Celejar wrote: > Package: wireguard-tools > Version: 0.0.20191212-1 > Severity: normal > > I use wireguard to establish a very simple point-to-point VPN. 'wg-quick > up wgo'

Bug#946996: wireguard-tools: 'wg-quick down' segfaults

2019-12-18 Thread Celejar
Package: wireguard-tools Version: 0.0.20191212-1 Severity: normal I use wireguard to establish a very simple point-to-point VPN. 'wg-quick up wgo' works fine; 'wg-quick down wg0' also seems to work correctly, but it segfaults after doing (AFAICT) everything that it's supposed to do. Everything