Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130825164220.2801654a@sibserver.ru>
Date: Sun, 25 Aug 2013 16:42:20 +0800
From: orc <orc@...server.ru>
To: musl@...ts.openwall.com
Subject: Re: dn_expand() confuses postfix

On Sun, 25 Aug 2013 02:43:21 -0400
Rich Felker <dalias@...ifal.cx> wrote:

> On Thu, Aug 15, 2013 at 02:14:22PM +0800, orc wrote:
> > Other issue now:
> > 
> > ../test_dns_lookup: lookup yandex.ru type MX flags 2
> > ../test_dns_lookup: dns_query: yandex.ru (MX): OK
> > ../test_dns_lookup: warning: valid_hostname: invalid character
> > 6(decimal): ?yande.?r ../test_dns_lookup: warning: malformed domain
> > name in resource name of MX record
> > for ?yande.?r: ?yande.?r ../test_dns_lookup: fatal: Name service
> > error for name=yandex.ru type=MX: Malformed or unexpected name
> > server reply
> > 
> > ../test_dns_lookup: lookup ya.ru type MX flags 2
> > ../test_dns_lookup: dns_query: ya.ru (MX): OK
> > ../test_dns_lookup: warning: valid_hostname: invalid character
> > 2(decimal): ?y.?r ../test_dns_lookup: warning: malformed domain
> > name in resource name of MX record
> > for ?y.?r: ?y.?r ../test_dns_lookup: fatal: Name service error for
> > name=ya.ru type=MX: Malformed or unexpected name server reply
> > 
> > temp buffer at src/dns/dns_lookup.c:287 is messed up with these.
> 
> I believe this was actually a nasty regression in the dn_expand "fix"
> -- somehow I thought my tests were checking reverse dns, but they
> weren't, and the new code actually had a bad off-by-one error. It
> should be fixed now. Let me know if you're still experiencing
> problems.
> 
> Rich

Yes, it works now. Thanks!

% ./test_dns_lookup mx google.com                                                                                              
./test_dns_lookup: lookup google.com type MX flags 2
./test_dns_lookup: dns_query: google.com (MX): OK
./test_dns_lookup: dns_get_answer: type MX for google.com
./test_dns_lookup: dns_get_answer: type MX for google.com
./test_dns_lookup: dns_get_answer: type MX for google.com
./test_dns_lookup: dns_get_answer: type MX for google.com
./test_dns_lookup: dns_get_answer: type MX for google.com
google.com: fqdn: google.com
google.com: ttl:       600 pref: 50 MX: alt4.aspmx.l.google.com
google.com: ttl:       600 pref: 40 MX: alt3.aspmx.l.google.com
google.com: ttl:       600 pref: 20 MX: alt1.aspmx.l.google.com
google.com: ttl:       600 pref: 10 MX: aspmx.l.google.com
google.com: ttl:       600 pref: 30 MX: alt2.aspmx.l.google.com

% ./test_dns_lookup mx ya.ru                                                                                                   
./test_dns_lookup: lookup ya.ru type MX flags 2
./test_dns_lookup: dns_query: ya.ru (MX): OK
./test_dns_lookup: dns_get_answer: type MX for ya.ru
ya.ru: fqdn: ya.ru
ya.ru: ttl:      6580 pref: 10 MX: mx.yandex.ru

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.