Skip Menu |

This queue is for tickets about the IO-Socket-SSL CPAN distribution.

Report information
The Basics
Id: 99448
Status: resolved
Priority: 0/
Queue: IO-Socket-SSL
People
Owner: Nobody in particular
Requestors: justincase [...] yopmail.com
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

History Show all quoted text
  Sun Oct 12 11:53:52 2014 justincase [...] yopmail.com - Ticket created
Subject: test failure on osx
I get this test failure on two different machines running different versions of OS X (10.9.5 and 10.7.5). not ok 71 - 1 != 0 |12345.6: cn=12345.6 san= # Failed test '1 != 0 |12345.6: cn=12345.6 san=' # at t/verify_hostname_standalone.t line 55. Perl v5.20.0 on both machines. I tested past versions until 1.986 where the test was first introduced and it failed the same test on each version. I don't see any similar test errors on the cpan testers reports page. $ cpanm Net::SSLeay Net::SSLeay is up to date. (1.66) $ openssl version OpenSSL 1.0.1i 6 Aug 2014 Please let me know if you need any other information from me.
  Tue Oct 21 11:18:24 2014 justincase [...] yopmail.com - Correspondence added
From: justincase [...] yopmail.com
On Sun Oct 12 11:53:52 2014, justincase wrote: Show quoted text
> I get this test failure on two different machines running different > versions of OS X (10.9.5 and 10.7.5). > > not ok 71 - 1 != 0 |12345.6: cn=12345.6 san= > # Failed test '1 != 0 |12345.6: cn=12345.6 san=' > # at t/verify_hostname_standalone.t line 55. > > Perl v5.20.0 on both machines. > > I tested past versions until 1.986 where the test was first introduced > and it failed the same test on each version. I don't see any similar > test errors on the cpan testers reports page. > > $ cpanm Net::SSLeay > Net::SSLeay is up to date. (1.66) > > $ openssl version > OpenSSL 1.0.1i 6 Aug 2014 > > Please let me know if you need any other information from me.
Just upgraded one of the machines to OS X 10.10 and built a new perl v5.20.1 with perlbrew and still getting the same test failure. Trawled through cpantesters and finally found another case with same failing test: http://www.cpantesters.org/cpan/report/bca3c748-2eda-11e4-9518-88ec160780b7
  Tue Oct 21 16:01:29 2014 Steffen_Ullrich [...] genua.de - Correspondence added
Am Di 21. Okt 2014, 11:18:24, justincase schrieb: Show quoted text
> On Sun Oct 12 11:53:52 2014, justincase wrote:
> > I get this test failure on two different machines running different > > versions of OS X (10.9.5 and 10.7.5). > > > > not ok 71 - 1 != 0 |12345.6: cn=12345.6 san= > > # Failed test '1 != 0 |12345.6: cn=12345.6 san=' > > # at t/verify_hostname_standalone.t line 55. > >
This is strange. I suspect that inet_aton('12345.6') on your system is returning true. Could you please try: perl -MSocket -e 'print inet_aton(q[12345.6])."\n"' | hexdump Regards, Steffen
  Tue Oct 21 16:01:29 2014 The RT System itself - Status changed from 'new' to 'open'
  Tue Oct 21 16:15:46 2014 justincase [...] yopmail.com - Correspondence added
From: justincase [...] yopmail.com
On Tue Oct 21 16:01:29 2014, SULLR wrote: Show quoted text
> Am Di 21. Okt 2014, 11:18:24, justincase schrieb:
> > On Sun Oct 12 11:53:52 2014, justincase wrote:
> > > I get this test failure on two different machines running different > > > versions of OS X (10.9.5 and 10.7.5). > > > > > > not ok 71 - 1 != 0 |12345.6: cn=12345.6 san= > > > # Failed test '1 != 0 |12345.6: cn=12345.6 san=' > > > # at t/verify_hostname_standalone.t line 55. > > >
> > > This is strange. > I suspect that inet_aton('12345.6') on your system is returning true. > Could you please try: > > perl -MSocket -e 'print inet_aton(q[12345.6])."\n"' | hexdump
$ perl -MSocket -e 'print inet_aton(q[12345.6])."\n"' | hexdump 0000000 c6 69 f4 e4 0a 0000005
  Tue Oct 21 16:24:41 2014 justincase [...] yopmail.com - Correspondence added
From: justincase [...] yopmail.com
On Tue Oct 21 16:15:46 2014, justincase wrote: Show quoted text
> On Tue Oct 21 16:01:29 2014, SULLR wrote:
> > Am Di 21. Okt 2014, 11:18:24, justincase schrieb:
> > > On Sun Oct 12 11:53:52 2014, justincase wrote:
> > > > I get this test failure on two different machines running different > > > > versions of OS X (10.9.5 and 10.7.5). > > > > > > > > not ok 71 - 1 != 0 |12345.6: cn=12345.6 san= > > > > # Failed test '1 != 0 |12345.6: cn=12345.6 san=' > > > > # at t/verify_hostname_standalone.t line 55. > > > >
> > > > > > This is strange. > > I suspect that inet_aton('12345.6') on your system is returning true. > > Could you please try: > > > > perl -MSocket -e 'print inet_aton(q[12345.6])."\n"' | hexdump
> > $ perl -MSocket -e 'print inet_aton(q[12345.6])."\n"' | hexdump > 0000000 c6 69 f4 e4 0a > 0000005
So this has to be a bug in Socket since this looks like it works properly: $ perl -MAnyEvent::Socket -e 'print AnyEvent::Socket::aton(q[12345.6])."\n"' | hexdump 0000000 0a 0000001
  Tue Oct 21 17:01:04 2014 Steffen_Ullrich [...] genua.de - Correspondence added
Show quoted text
> > $ perl -MSocket -e 'print inet_aton(q[12345.6])."\n"' | hexdump > 0000000 c6 69 f4 e4 0a > 0000005
OK, I've seen this kind of problem before on other *BSD and don't know if it is a bug in Perl or libc. With certain DNS setups inet_aton will do a DNS lookup, even if the given name cannot be a hostname. In your case you are probably behind Time Warner network which resolves anything unresolvable to a landing page at 198.105.244.228 ("www.dnsrsearch.com"). With 2.002 I no longer use inet_aton and thus the issue should be resolved. Regards, Steffen
  Tue Oct 21 17:01:05 2014 Steffen_Ullrich [...] genua.de - Status changed from 'open' to 'resolved'