[Opendnssec-develop] Re: [OpenDNSSEC] #21: nsec3er can't handle an "Empty non-terminal" at the start of the file

[OpenDNSSEC]

#21: nsec3er can't handle an "Empty non-terminal" at the start of the file
----------------------------------------+-----------------------------------
Reporter:  opendnssec.simon at arlott.org  |        Owner:  matthijs
    Type:  defect                       |       Status:  accepted
Priority:  major                        |    Component:  Signer  
 Version:  1.0a1                        |   Resolution:          
Keywords:                               |  
----------------------------------------+-----------------------------------

Comment(by opendnssec.simon at arlott.org):

 The original zone that caused the problem is an ip6.arpa zone, which
 unlike most in-addr.arpa zone files contains multiple levels of hostname
 parts, e.g.
 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa.
 IN PTR localhost.

 Example zone file "test":
 {{{
 $ cat > test.input
 @ SOA . . ( 1 1 1 1 1 )
 1.2.3.4 PTR .

 $ src/OpenDNSSEC-1.0a3/signer/tools/zone_reader -o test -w test.sorted -n
 -s 00 -t 5 -a 1 < test.input

 $ cat test.sorted
 ; Empty non-terminal: 4.test.
 1.2.3.4.test.   3600    IN      PTR     .
 test.   3600    IN      SOA     . . 1 1 1 1 1
 test.   3600    IN      NSEC3PARAM      1 0 5 00
 ; Empty non-terminal: 2.3.4.test.
 ; Empty non-terminal: 3.4.test.

 $ src/OpenDNSSEC-1.0a3/signer/tools/nsec3er -o test -s 00 -t 5 -a 1 -i
 test.sorted -w test.nsec
 Segmentation fault

 $
 }}}

-- 
Ticket URL: <http://trac.opendnssec.org/ticket/21#comment:3>
OpenDNSSEC <http://www.opendnssec.org/>
OpenDNSSEC