[Bug 1215093] Re: "Bad NSEC data" when using zonesigner -usensec3

2014-06-25 Thread Matthias Geiser
I can confirm bug and workaround for ubuntu 14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215093 Title: "Bad NSEC data" when using zonesigner -usensec3 To manage notifications about this b

[Bug 1215093] Re: "Bad NSEC data" when using zonesigner -usensec3

2014-02-24 Thread Nuno Sucena Almeida
Also hitting the same issue, ubuntu 13.10. The workaround posted above worked for me, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215093 Title: "Bad NSEC data" when using zonesigner -usen

[Bug 1215093] Re: "Bad NSEC data" when using zonesigner -usensec3

2013-09-30 Thread Juan Orti Alcaine
I have hit the same problem and your fix works perfect for me (both the command line parameter, and the config file). Thank you for you work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215093 Tit

[Bug 1215093] Re: "Bad NSEC data" when using zonesigner -usensec3

2013-08-21 Thread TJ
My last statement is incorrect: the patch to "dnssec-tools.conf" is not sufficient. Apparently the contents of that file are only read by the tools if their command-lines are empty. That means that zonesigner needs its set of options amended as previously described: # zonesigner -szopts "-O full"

[Bug 1215093] Re: "Bad NSEC data" when using zonesigner -usensec3

2013-08-21 Thread TJ
After further investigation it appears that the default output of "dnssec-signzone" (part of the bind9 package) is causing the issue. That tool has the "-O" output-format option which defaults to "text" but can be "full" or "raw". It appears that the default "text" mode wraps lines as well as leav

[Bug 1215093] Re: "Bad NSEC data" when using zonesigner -usensec3

2013-08-21 Thread TJ
I've tracked the error down to "/usr/share/perl5/Net/DNS/ZoneFile/Fast.pm". It has three tests which all report "bad NSEC data" so I added unique numbers into each error message. The 2nd one generates the error. It appears the fault is in the regular expression. The code is: } elsif (/\G(nse