On 1/17/20 10:26 AM, Alexander E. Patrakov wrote:
>
> Great! Could you please make sure that the fix somehow propagates to
> Debian stable?
>
It is somehow propagated to stable, in the form a backport available:
iptables 1.8.3-2~bpo10+1
I don't plan, nor have time, to work on identifying the
Control: fixed -1 1.8.3-2
On 1/16/20 11:10 PM, Alexander E. Patrakov wrote:
> Package: iptables
> Version: 1.8.2-4
Thanks for the bug report!
I couldn't reproduce this in a more recent version:
=== 8< ===
arturo@endurance:~ $ sudo iptables-nft-restore < original_rules.iptables
arturo@endurance:
On Fri, Jan 17, 2020 at 2:25 PM Arturo Borrero Gonzalez
wrote:
>
> Control: fixed -1 1.8.3-2
>
> On 1/16/20 11:10 PM, Alexander E. Patrakov wrote:
> > Package: iptables
> > Version: 1.8.2-4
>
> Thanks for the bug report!
>
> I couldn't reproduce this in a more recent version:
>
> === 8< ===
> artu
Package: iptables
Version: 1.8.2-4
Severity: normal
Dear maintainer,
This is a reproducible way to segfault iptables-restore (the nftables variant):
0. Start with a blank state.
1. Load the initial rules:
iptables-restore < original_rules.iptables
2. Attempt to test new rules, to be appli
4 matches
Mail list logo
