You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2009/11/05 17:49:58 UTC
[Bug 6232] Net::DNS inconsistent in use of presentation/wire format
in packets, breaks DnsResolver
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6232
Mark Martinec <Ma...@ijs.si> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Undefined |3.3.0
--- Comment #1 from Mark Martinec <Ma...@ijs.si> 2009-11-05 08:49:57 UTC ---
A possible trick is to convert our query domain into its presentation form
when creating a Net::DNS::Packet object, by using undocumented procedure
presentation2wire or stripdot in Net::DNS. The following change
to the above test program appears to provide consistent results:
query(Net::DNS::stripdot(
"\xE6\x97\xA5\xE6\x9C\xAC\xE8\xAA\x9E.jp.multi.uribl.com"));
result:
\230\151\165\230\156\172\232\170\158.jp.multi.uribl.com
query: \230\151\165\230\156\172\232\170\158.jp.multi.uribl.com
reply: \230\151\165\230\156\172\232\170\158.jp.multi.uribl.com
Now, the question is, what was meant by authors of Net::DNS.
To me it seems more logical to keep raw bytes in the Net::DNS::Packet
object, and do the decoding/encoding in the interface routines
if necessary. If that is indeed the case, the above workaround
would break this, and a potential fix to Net::DNS could break our
workaround.
Do we have any contacts with Net::DNS guys?
--
Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.