Report information
The Basics
Id:
45352
Status:
resolved
Priority:
Medium/Medium
Queue:

People
Owner:
Nobody in particular
Cc:
AdminCc:

BugTracker
Version Fixed:
9.9.11, 9.9.11-S1, 9.10.6, 9.10.6-S1, 9.11.2, 9.12.0
Version Found:
(no value)
Versions Affected:
(no value)
Versions Planned:
(no value)
Priority:
P2 Normal
Severity:
S2 Normal
CVSS Score:
(no value)
CVE ID:
(no value)
Component:
Other
Area:
Other

Dates
Created:Wed, 07 Jun 2017 10:19:55 -0400
Updated:Fri, 28 Jul 2017 23:05:44 -0400
Closed:Sun, 11 Jun 2017 08:10:05 -0400



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: [PATCH] Not matching regexp for check5011.pl
Date: Wed, 7 Jun 2017 16:19:47 +0200
To: bind-bugs@isc.org
From: "Petr Menšík" <pemensik@redhat.com>
Hi! I was trying check5011.pl script to test validity of trust anchors in my bind file. I have found that it does not parse well recent dig +multiline output of dig. Before alg always ended without space, but at least from version 9.10.4 there is space present. Now: ; KSK; alg = RSASHA256 ; key id = 19036 Before: ; KSK; alg = RSASHA256; key id = 19036 check5011.pl does silently fail to parse alg and key id. Uses previous values from DNSKEY flags instead. It is not print helpful results then. I am sending patch that accepts both versions. Petr Menšík
Subject: Re: [ISC-Bugs #45352] AutoReply: [PATCH] Not matching regexp for check5011.pl
Date: Wed, 7 Jun 2017 16:28:13 +0200
To: bind9-bugs@isc.org
From: "Petr Menšík" <pemensik@redhat.com>
I am sorry, it did not attach the patch, so at least now. Dne 7.6.2017 v 16:19 BIND9 Bugs via RT napsal(a): > Greetings, > > This message was automatically generated to acknowledge receipt of > your recent email > "[PATCH] Not matching regexp for check5011.pl", > and to let you know that we have opened a ticket for your request > (a summary of which appears below.) > > We do not need a further response from you, but if you do respond, > please include in the Subject of your reply the ID > '[ISC-Bugs #45352]' > so that we can match up your reply with our trouble ticket. > > What Happens Next > ================= > > Bug reports submitted to us in this manner are handled based on > perceived severity in relation to other bugs. We handle reports as > time permits so there is no guaranteed response time for these > reports. > > If you feel the issue you are reporting is a security issue, please > see http://www.isc.org/security/reporting-issues for details on how > to report it, including the PGP key you may use. > > If it is of a non-security yet still urgent matter, you may reply > to this message to add further information. > > > Other Support Options > ===================== > > If your organization requires more immediate attention, ISC offers > paid support options. Please see http://www.isc.org/services/support > for more information. > > If paid support is not an option, please consider making a donation > to ISC. We don't require a donation -- we will work on your report > just as quickly whether or not you can donate -- but we always need > and welcome community support. See http://www.isc.org/supportisc > > > Run a Supported Version > ======================= > > If you are not running a supported version of BIND, please upgrade. > Bug reports against unsupported versions of BIND are discouraged, > as your issue may have already been addressed. > > You can find the latest version of BIND here: > > https://www.isc.org/software/bind > > > For configuration help... > ========================= > > Questions regarding configuration or setup of BIND are addressed on > the bind-users list - to subscribe, visit: > > https://lists.isc.org/mailman/listinfo/bind-users > > > Thank you, > bind9-bugs@isc.org > > --------------------------------------------------------------------- > > Hi! > > I was trying check5011.pl script to test validity of trust anchors in my > bind file. I have found that it does not parse well recent dig > +multiline output of dig. > > Before alg always ended without space, but at least from version 9.10.4 > there is space present. > > Now: > ; KSK; alg = RSASHA256 ; key id = 19036 > > Before: > ; KSK; alg = RSASHA256; key id = 19036 > > check5011.pl does silently fail to parse alg and key id. Uses previous > values from DNSKEY flags instead. It is not print helpful results then. > > I am sending patch that accepts both versions. > > Petr Menšík > >

Message body is not shown because sender requested not to inline it.