From wouter at NLnetLabs.nl Mon Feb 2 10:21:11 2009 From: wouter at NLnetLabs.nl (W.C.A. Wijngaards) Date: Mon, 02 Feb 2009 11:21:11 +0100 Subject: [ldns-users] [Unbound-users] Titanium bug in unbound or ldns? In-Reply-To: References: Message-ID: <4986C917.90301@nlnetlabs.nl> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hoi Paul, RR_TYPE_DLV has been added somewhat recently to ldns (so that unbound could support DLV). Do you have multiple ldns installations on the computer, and it is picking an older ldns installation that did not have the DLV typecode (or NSEC3 stuff) yet? Best regards, Wouter Paul Wouters wrote: > Hey, > > While trying to build unbound-1.2.0rc1 on an Itanium, we run into strange > bugs in the include files. I suspect either ldns or unbound got things > wrong. > > The first error that shows up is: > > gcc -I. -I. -I/usr/include -I/usr/include -I/include -DHAVE_CONFIG_H -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -D_GNU_SOURCE -c services/cache/dns.c -fPIC -DPIC -o build/services/cache/.libs/dns.o > services/cache/dns.c: In function 'dns_cache_lookup': > services/cache/dns.c:568: error: 'LDNS_RR_TYPE_DLV' undeclared (first use in this function) > services/cache/dns.c:568: error: (Each undeclared identifier is reported only once > services/cache/dns.c:568: error: for each function it appears in.) > make: *** [build/services/cache/dns.lo] Error 1 > error: Bad exit status from /var/tmp/rpm-tmp.15014 (%build) > > > This is odd, because LDNS_RR_TYPE_DLV and others are found in > which is installed (from ldns-1.4.0 not the shipped copy within unbound) > > Fixing this manually, its runs into further similar issues with NSEC3 > related defines. > > I can provide config.log, config.status and/or access :) > > Paul > _______________________________________________ > Unbound-users mailing list > Unbound-users at unbound.net > http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkmGyRcACgkQkDLqNwOhpPgufQCeNem57X5Af957xdpLWOqGNf31 p+YAn0pY1silNCyQtR4Mgo5idiegjOP0 =tjhx -----END PGP SIGNATURE----- From jelte at NLnetLabs.nl Mon Feb 9 22:42:22 2009 From: jelte at NLnetLabs.nl (Jelte Jansen) Date: Mon, 09 Feb 2009 23:42:22 +0100 Subject: [ldns-users] ldns 1.5.0 release announcement Message-ID: <4990B14E.5000008@NLnetLabs.nl> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've just put up the tarball of ldns 1.5.0. Get it while it's hot! Project page: http://www.nlnetlabs.nl/projects/ldns/ Direct download: http://www.nlnetlabs.nl/downloads/ldns/ldns-1.5.0.tar.gz sha1sum: b4e81f195902127e4f03f04ea57fd51d57d59c67 Have fun, Jelte - -------------------- Changelog: 1.5.0 Bug fixes: * fixed a possible memory overflow in the RR parser * build flag fix for Sun Studio * fixed a building race condition in the copying of header files * EDNS0 extended rcode; the correct assembled code number is now printed (still in the EDNS0 field, though) * ldns_pkt_rr no longer leaks memory (in fact, it no longer copies anything all) API addition: * ldns_key now has support for 'external' data, in which case the OpenSSL EVP structures are not used; ldns_key_set_external_key() and ldns_key_external_key() * added ldns_key_get_file_base_name() which creates a 'default' filename base string for key storage, of the form "K++" * the ldns_dnssec_* family of structures now have deep_free() functions, which also free the ldns_rr's contained in them * there is now an ldns_match_wildcard() function, which checks whether a domain name matches a wildcard name * ldns_sign_public has been split up; this resulted in the addition of ldns_create_empty_rrsig() and ldns_sign_public_buffer() Examples: * ldns-signzone can now automatically add DNSKEY records when using an OpenSSL engine, as it already did when using key files * added new example tool: ldns-nsec3-hash * ldns-dpa can now filter on specific query name and types * ldnsd has fixes for the zone name, a fix for the return value of recvfrom(), and an memory initialization fix (Thanks to Colm MacC?rthaigh for the patch) * Fixed memory leaks in ldnsd -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmQsU4ACgkQ4nZCKsdOncU/7QCdFUAncKjg7eZWkgfovQrLVw5v j94An181/6yVu3fgMy/nuuyj4R/yjq3m =9Qon -----END PGP SIGNATURE----- From jelte at NLnetLabs.nl Tue Feb 10 17:53:03 2009 From: jelte at NLnetLabs.nl (Jelte Jansen) Date: Tue, 10 Feb 2009 18:53:03 +0100 Subject: [ldns-users] release early, release often: ldns 1.5.1 release announcement Message-ID: <4991BEFF.4090508@NLnetLabs.nl> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, to my great embarrassment, a major bug snuck past me in one of the more important example tools of ldns 1.5.0. The zone signer was broken to the point of unusability; it gave an assertion failure in probably most real-world scenarios. So before everyone is done packaging and installing it; I've put up ldns-1.5.1 for download. There are no changes in the library itself; apart from the removal of two wrong warning messages in the build scripts the only change from 1.5.0 is the multiple key fix in examples/ldns-signzone.c. My apologies, Jelte Project page: http://www.nlnetlabs.nl/projects/ldns Direct download: http://www.nlnetlabs.nl/downloads/ldns/ldns-1.5.1.tar.gz Sha1sum: 070210a417633b7358bb3466da40e6f1872f36c2 - ----------- Changelog: 1.5.1 Example tools: * ldns-signzone was broken in 1.5.0 for multiple keys, this has been repaired Build system: * Removed a small erroneous output warning in examples/configure and drill/configure -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmRvv8ACgkQ4nZCKsdOncVd1ACgtg2qNCUenZT7F5eVm16702BC AggAoLVbuVVYSTmNoZL+G7+sa+uTGCiD =9ma6 -----END PGP SIGNATURE----- From takahiko at iij.ad.jp Wed Feb 11 13:49:07 2009 From: takahiko at iij.ad.jp (SUZUKI Takahiko) Date: Wed, 11 Feb 2009 22:49:07 +0900 (JST) Subject: [ldns-users] [request] SPF RR support Message-ID: <20090211.224907.68547085.takahiko@iij.ad.jp> Hi, I have a request for support SPF RR. As you probably know, SPF RR is defined in RFC4408, and listed in IANA Registry: http://www.ietf.org/rfc/rfc4408.txt http://www.iana.org/assignments/dns-parameters The format of SPF RR is the same as TXT RR (see RFC4408 3.1.1. DNS Resource Record Types). I've tried to make a patch to support SPF RR, but I don't know that this patch is sufficient or not. I attached the patch. Please try this. Regards, Takahiko -- SUZUKI Takahiko Development and Operation Section, Messaging Service Division, Internet Initiative Japan Inc. -------------- next part -------------- diff -ur ldns-1.5.1.orig/ldns/rr.h ldns-1.5.1/ldns/rr.h --- ldns-1.5.1.orig/ldns/rr.h 2008-11-05 19:00:32.000000000 +0900 +++ ldns-1.5.1/ldns/rr.h 2009-02-11 21:49:33.261429097 +0900 @@ -175,6 +175,9 @@ LDNS_RR_TYPE_NSEC3 = 50, LDNS_RR_TYPE_NSEC3PARAMS = 51, + /** RFC4408 */ + LDNS_RR_TYPE_SPF = 99, + LDNS_RR_TYPE_UINFO = 100, LDNS_RR_TYPE_UID = 101, LDNS_RR_TYPE_GID = 102, diff -ur ldns-1.5.1.orig/libdns.vim ldns-1.5.1/libdns.vim --- ldns-1.5.1.orig/libdns.vim 2006-07-04 21:50:41.000000000 +0900 +++ ldns-1.5.1/libdns.vim 2009-02-11 21:49:33.261815925 +0900 @@ -231,6 +231,7 @@ syn keyword ldnsConstant LDNS_RR_TYPE_A6 syn keyword ldnsConstant LDNS_RR_TYPE_SINK syn keyword ldnsConstant LDNS_RR_TYPE_IPSECKEY +syn keyword ldnsConstant LDNS_RR_TYPE_SPF syn keyword ldnsConstant LDNS_RR_TYPE_UINFO syn keyword ldnsConstant LDNS_RR_TYPE_UID syn keyword ldnsConstant LDNS_RR_TYPE_GID diff -ur ldns-1.5.1.orig/rr.c ldns-1.5.1/rr.c --- ldns-1.5.1.orig/rr.c 2009-02-03 18:17:32.000000000 +0900 +++ ldns-1.5.1/rr.c 2009-02-11 21:49:33.262990460 +0900 @@ -1950,7 +1950,8 @@ {LDNS_RR_TYPE_NULL, "TYPE96", 1, 1, type_0_wireformat, LDNS_RDF_TYPE_NONE, LDNS_RR_NO_COMPRESS, 0 }, {LDNS_RR_TYPE_NULL, "TYPE97", 1, 1, type_0_wireformat, LDNS_RDF_TYPE_NONE, LDNS_RR_NO_COMPRESS, 0 }, {LDNS_RR_TYPE_NULL, "TYPE98", 1, 1, type_0_wireformat, LDNS_RDF_TYPE_NONE, LDNS_RR_NO_COMPRESS, 0 }, -{LDNS_RR_TYPE_NULL, "TYPE99", 1, 1, type_0_wireformat, LDNS_RDF_TYPE_NONE, LDNS_RR_NO_COMPRESS, 0 }, + /* 99 */ + {LDNS_RR_TYPE_SPF, "SPF", 1, 0, NULL, LDNS_RDF_TYPE_STR, LDNS_RR_NO_COMPRESS, 0 }, {LDNS_RR_TYPE_NULL, "TYPE100", 1, 1, type_0_wireformat, LDNS_RDF_TYPE_NONE, LDNS_RR_NO_COMPRESS, 0 }, {LDNS_RR_TYPE_NULL, "TYPE101", 1, 1, type_0_wireformat, LDNS_RDF_TYPE_NONE, LDNS_RR_NO_COMPRESS, 0 }, {LDNS_RR_TYPE_NULL, "TYPE102", 1, 1, type_0_wireformat, LDNS_RDF_TYPE_NONE, LDNS_RR_NO_COMPRESS, 0 }, From deepak.joshi at impetus.co.in Thu Feb 26 10:06:09 2009 From: deepak.joshi at impetus.co.in (Deepak Joshi) Date: Thu, 26 Feb 2009 15:36:09 +0530 Subject: [ldns-users] no message compression Message-ID: Hello Everyone, I am using ldns-1.3.0 and I am creating an ldns_pkt packet and using ldns_pkt2wire() to create buffer, but it does not apply the message compression as defined in rfc-1035 (section 4.1.4). I am unable to find any documentation for the same. Am I missing something to enable the compression. Please advice. Thanks, Deepak ________________________________ * Meet us at Booth 6344, at the CTIA, Las Vegas, Mar 31-Apr 3, 2009. * Attend the iLabs webinar on High Performance Computing on Mar 13, 2009. Visit www.impetus.com for details. Impetus is the winner of the GSMA's 2009 Mobile Innovation Global Award and the Economic Times Intel Smart Workplace Awards 2008. NOTE: This message may contain information that is confidential, proprietary, privileged or otherwise protected by law. The message is intended solely for the named addressee. If received in error, please destroy and notify the sender. Any use of this email is prohibited when received in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jelte at NLnetLabs.nl Thu Feb 26 11:08:39 2009 From: jelte at NLnetLabs.nl (Jelte Jansen) Date: Thu, 26 Feb 2009 12:08:39 +0100 Subject: [ldns-users] no message compression In-Reply-To: References: Message-ID: <49A67837.7050009@NLnetLabs.nl> Deepak Joshi wrote: > Hello Everyone, > > I am using ldns-1.3.0 and I am creating an ldns_pkt packet and > using ldns_pkt2wire() to create buffer, but it does not apply the > message compression as defined in rfc-1035 (section 4.1.4). > > I am unable to find any documentation for the same. Am I missing > something to enable the compression. > you are not missing anything, message compression is just not implemented in the ldns 2wire functions. I could put it on the todo list as a feature request. Jelte -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 260 bytes Desc: OpenPGP digital signature URL: