Bug #131579 for Net-DNS: Parse issue in Net::DNS::RR->token

Mon Jan 27 23:17:46 2020 rwf [...] loonybin.net - Ticket created

Subject:	Parse issue in Net::DNS::RR->token
Date:	Mon, 27 Jan 2020 23:07:38 -0500 (EST)
To:	bug-Net-DNS [...] rt.cpan.org
From:	Rob Foehl <rwf [...] loonybin.net>

There appears to be an issue with splitting certain strings containing semicolons due to the current value of $PARSE_REGEX as used in Net::DNS::RR->token, e.g. TXT rdata. Simple reproducer and workaround: ╶➤ perl -MNet::DNS -le 'print Net::DNS::RR->new(name => "example.com", type => "TXT", txtdata => "x=1;y=2")->plain' example.com. IN TXT x=1\ ╶➤ perl -MNet::DNS -le 'print Net::DNS::RR->new(name => "example.com", type => "TXT", txtdata => "x=1; y=2")->plain' example.com. IN TXT "x=1; y=2" That erroneous backslash is the last character output, and the rest of the string is also unavailable when token is called in list context. Issue confirmed in at least 1.19 and 1.21, haven't checked other versions. -Rob

Tue Jan 28 07:18:56 2020 rwfranks [...] acm.org - Correspondence added

On Mon Jan 27 23:17:46 2020, rwf@loonybin.net wrote: Show quoted text

> There appears to be an issue with splitting certain strings containing > semicolons due to the current value of $PARSE_REGEX as used in > Net::DNS::RR->token

Good catch.

Tue Jan 28 07:18:57 2020 The RT System itself - Status changed from 'new' to 'open'

Mon Feb 03 10:51:18 2020 rwfranks [...] acm.org - Correspondence added

On Tue Jan 28 07:18:56 2020, rwfranks@acm.org wrote: Fixed in 1.21_01

Mon Feb 03 10:51:20 2020 rwfranks [...] acm.org - Fixed in 1.21_01 added

Thu Feb 13 12:44:35 2020 rwf [...] loonybin.net - Correspondence added

Subject:	Re: [rt.cpan.org #131579] Parse issue in Net::DNS::RR->token
Date:	Thu, 13 Feb 2020 12:44:29 -0500 (EST)
To:	Dick Franks via RT <bug-Net-DNS [...] rt.cpan.org>
From:	Rob Foehl <rwf [...] loonybin.net>

Confirmed fixed in 1.22. Thanks! -Rob

Wed Feb 19 07:15:01 2020 NLNETLABS [...] cpan.org - Status changed from 'open' to 'resolved'