I wanted to build an awesome place for people to discuss module specific issues, but I don't have any more time for this, and there are much better places to discuss Perl-related issues. I'd recommend asking your question on Stack Overflow or on Perl Monks.
If you are looking for a Perl tutorial or Perl-related news, I hope these links will serve you well.
Posted on 2008-06-11 22:45:57-07 by kkline
IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)
Currently running latest Bundle:CPAN W/ cpan[15] install IO::Socket IO::Socket is up to date (1.30). + cpan[16] install IO::Socket::SSL IO::Socket::SSL is up to date (1.13). + cpan[17] install IO::Socket::INET IO::Socket::INET is up to date (1.31). Using Scanlite.pm in conjunction with SSL.pm absolutely no problems until now with release of Nessu +s 3.2.1 On every distro I have tried / tested (Redhat EL4/Fedora/Mandriva 2008) I now get the following err +or with test script [root@fs1 tmp]# ./test.pl CA file certs/my-ca.pem not found, using CA path instead. DEBUG: /usr/lib/perl5/site_perl/5.8.8/IO/Socket/SSL.pm:1010: IO::Socket::SSL::SSL_Context HASH(0x72 +7ac0) DEBUG: /usr/lib/perl5/site_perl/5.8.8/IO/Socket/SSL.pm:1128: new ctx 11779744 IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0) at ./test.pl line 19 DEBUG: /usr/lib/perl5/site_perl/5.8.8/IO/Socket/SSL.pm:1163: free ctx 11779744 open=11779744 DEBUG: /usr/lib/perl5/site_perl/5.8.8/IO/Socket/SSL.pm:1166: OK free ctx 11779744 Nessus login failed %d: %s 1Connect to 192.168.0.250:1241 failed. (IO::Socket::INET configuration failederror:00000000:lib(0): +func(0):reason(0)) at ./test.pl line 44. #!/usr/bin/perl use Net::Nessus::ScanLite; my $nessushost = "localhost"; my $nessusport = "1241"; my $nessus = Net::Nessus::ScanLite->new( host => $nessushost, port => $nessusport, ssl => 1 # comment or set to 1 out if using ssl ); $nessus->preferences( { host_expansion => 'none', safe_checks => 'yes', checks_read_timeout => 1 + }); $nessus->plugin_set("10835;10861;11808;11921;11790"); my $addr = "10.0.0.1"; if( $nessus->login("inprotect", "inprotect" ) ) { $nessus->attack($addr); printf("Total info's = %d\n",$nessus->total_info); foreach( $nessus->info_list ) { my $info = $_; printf("Info:\nID: %s\nPort: %s\nDessc: %s\n", $info->ScanID, $info->Port, $info->Description); } printf("Total hole's = %d\n",$nessus->total_holes); foreach( $nessus->hole_list ) { my $info = $_; printf("Info:\nID: %s\nPort: %s\nDessc: %s\n", $info->ScanID, $info->Port, $info->Description); } } else { die("Nessus login failed %d: %s\n",$nessus->code,$nessus->error); } Should be SSL_version = TLSv1 would something have changed that is affecting SSL implementation or a bug exists in Scanlite.pm or + SSL.pm code that was a little more forgiving in previous versions of Nessus?
Direct Responses: 8064 | Write a response
Posted on 2008-06-12 12:33:27-07 by noxxi in response to 8060
Re: IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)
older versions of IO::Socket::SSL ignored Timeout parameter for the SSL handshake, e.g they blocked until the SSL handshake was done. Net::Nessus::ScanLite seems to use a very short timeout of only 1 (man page says 3, but code says 1), so maybe it would help to increase the timeout.
Direct Responses: 8071 | Write a response
Posted on 2008-06-12 20:48:18-07 by kkline in response to 8064
Re: IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)
I was considering the timeout as a problem by setting it to five got new outpt warns of handshake problem haven't research that yet. found a quite lengthy article about debian where libssl may be the culprit http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=338006
[root@fs1 tmp]# ./test.pl CA file certs/my-ca.pem not found, using CA path instead. DEBUG: /usr/lib/perl5/site_perl/5.8.8/IO/Socket/SSL.pm:1010: IO::Socket::SSL::SSL_Context HASH(0x72 +66c0) DEBUG: /usr/lib/perl5/site_perl/5.8.8/IO/Socket/SSL.pm:1128: new ctx 11780016 SSL connect attempt failed because of handshake problemserror:00000000:lib(0):func(0):reason(0) at ./test.pl line 21 DEBUG: /usr/lib/perl5/site_perl/5.8.8/IO/Socket/SSL.pm:1163: free ctx 11780016 open=11780016 DEBUG: /usr/lib/perl5/site_perl/5.8.8/IO/Socket/SSL.pm:1166: OK free ctx 11780016 IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0) at ./test.pl line 21 Nessus login failed %d: %s 1Connect to localhost:1241 failed. (IO::Socket::INET configuration failederror:00000000:lib(0):func +(0):reason(0)) at ./test.pl line 46.
Direct Responses: 8072 | Write a response
Posted on 2008-06-12 22:51:39-07 by kkline in response to 8071
Re: IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)
I tested on a variety of my boxes redhat EL4 is now working with the timeout increased currently got mandriva provided the handshake problem may have mucked up an setting in the nessusd.config that is making it mad. Will update once I know more
Direct Responses: 8073 | Write a response
Posted on 2008-06-13 00:28:42-07 by kkline in response to 8072
Re: IO::Socket::INET configuration failederror:00000000:lib(0):func(0):reason(0)
Ok, that was the issue, I had muxed up the scanlite.pm modules trying some stuff which caused the one system to have a handshake issue after the timeout issue was fixed. Thanks for the help. Ken
Direct Responses: Write a response