Bug 613 - can not read a nsec3 record correctly when using Tab to separate different types in it
can not read a nsec3 record correctly when using Tab to separate different ty...
Status: RESOLVED FIXED
Product: ldns
Classification: Unclassified
Component: library
1.6.x
Other Linux
: P5 normal
Assigned To: LDNS dev team
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-09-29 08:43 CEST by Xiali Yan
Modified: 2014-09-29 11:02 CEST (History)
2 users (show)

See Also:


Attachments
screenshot of the zonefile and query result (108.43 KB, image/png)
2014-09-29 08:43 CEST, Xiali Yan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Xiali Yan 2014-09-29 08:43:11 CEST
Created attachment 261 [details]
screenshot of the zonefile and query result

If Tab is used in a nsec3 record to separate different types in it in a zonefile, ldns will ignore the types after the Tab in RDATA of the nsec3 record. For example:

0p9mhaveqvm6t7vbl5lop2u3t2rp3tom.example. NSEC3 1 1 12 aabbccdd (          
                            2t7b4g4vsa5smi47k61mv5bv1a22bojr MX DNSKEY
                            NS(Tab)SOA NSEC3PARAM RRSIG )

We'll get a incomplete nsec3 record in a dnssec query as follows:

0p9mhaveqvm6t7vbl5lop2u3t2rp3tom.example. NSEC3 1 1 12 aabbccdd (          
                            2t7b4g4vsa5smi47k61mv5bv1a22bojr NS MX DNSKEY

But, if we change Tab into Space, we'll get right answer.
For more information, see the attachment below.


Thank you.
Comment 1 Willem Toorop 2014-09-29 11:02:42 CEST
Thank you Xiali Yan,

Fix committed on the develop branch of our git repository:
http://git.nlnetlabs.nl/ldns/commit/?h=develop&id=d41a6c62

Kind regards,

-- Willem Toorop