netdev - Re: [PATCH iproute2] tc/lexer: let quotes actually start strings

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180124085148.0cc2cefe@xeon-e3>
Date:   Wed, 24 Jan 2018 08:51:48 -0800
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Wolfgang Bumiller <w.bumiller@...xmox.com>
Cc:     netdev@...r.kernel.org
Subject: Re: [PATCH iproute2] tc/lexer: let quotes actually start strings

On Mon, 22 Jan 2018 11:53:46 +0100
Wolfgang Bumiller <w.bumiller@...xmox.com> wrote:

> The lexer will go with the longest match, so previously
> the starting double quotes of a string would be swallowed by
> the [^ \t\r\n()]+ pattern leaving the user no way to
> actually use strings with escape sequences.
> Fix this by not allowing this case to start with double
> quotes.
> 
> Signed-off-by: Wolfgang Bumiller <w.bumiller@...xmox.com>

Looks good, applied.
Don't think ematch is that widely used; or someone would have noticed.