Re: nft list sets changed behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 18 Jun 2023 17:21:38 +0200
Pablo Neira Ayuso <pablo@xxxxxxxxxxxxx> wrote:

> On Sun, Jun 18, 2023 at 03:35:09PM +0200, Florian Westphal wrote:
> > moving to nf-devel
> > 
> > nft.ogxzcrqhuhgchbvxcs4j7wws@xxxxxxxxxxxxxxxxxxxxxx <nft.ogxzcrqhuhgchbvxcs4j7wws@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> [...]
> > > > > After updating to Debian 12 my tools relying on 'nft -j list sets' fail.
> > > > > It now does not include the elements in those lists like it did on 11.
> > 
> > I see three possible solutions:
> > 1 - accept the breakage.
> > 2 - repair the inconsistency so we get 1.0.0 and
> >     earlier behaviour back.
> > 3 - make "list sets" *always* include set elements,
> >     unless --terse was given.
> > 
> > Thoughts? I'd go with 3, I dislike the
> > different behaviour that 2) implies and we already
> > have --terse, we just need to make use of it here.
> 
> I'd go with 3 too, so --terse is honored.

I think so too. While there is a theoretical risk of breaking someone's script in the case that they were relying upon the 'new' behaviour, the present behaviour makes very little sense.

-- 
Kerin Millar



[Index of Archives]     [Netfitler Users]     [Berkeley Packet Filter]     [LARTC]     [Bugtraq]     [Yosemite Forum]

  Powered by Linux