IO::Socket::SSL 1

[kmowens]

I have a Java server that accepts SSL connections over a particular socket (using 9008 and 443) from a browser and exchanges data with no problems.

I have a Perl client that will connect to a web server using HTTPS with no problems.

The Java server is a middle-tier that needs to accept SSL connections from Perl scripts, but the Perl side fails during
IO::Socket::SSL->new(PeerAddr => 'xxx.xxx.xxx.xx:9008',
Proto => 'tcp',
SSL_use_cert => 0,
SSL_verify_mode => 0,
Timeout => 5
);

With debug on I get this not very informative answer
IO::Socket::INET configuration failed at ./test1.pl line 37.

Does anyone have a clue where I might start on solving this issue?

 

[PaulTEG]

           SSL_use_cert => 0,
           SSL_verify_mode => 0,

might need different values for https connects here

Bluffing like a big bluffing thing, but yours was the last with no reponses ...

Hope I brought a ray of sunshine ... if not ignore, I won't lose sleep ... come to think of it how do you lose sleep ... I know its here somewhere, I just put it down for a minute ...

I digress, it might be that, or it could be something completely different ... like a NEW parrot sketch ...

It's important in life to always strike a happy medium, so if you see someone with a crystal ball, and a smile on their face ...

 

[kmowens]

Paul,thanks for the input, but it probably isn't the SSL_use_cert or SSL_verify_mode.

SSL_use_cert forces the client to use a certificate of its own.

SSL_verify_mode "This option sets the verification mode for the peer certificate." I'm not sure what this means, but I think it might mean that it validates the certificate (certificate matches dns entry) of the server I'm connecting to. Since this is a sloppily self-signed certificate, I don't want that.

But the Perl client will connect with any web server with an ssl connection.

The Java server will connect with any browser making a ssl connection.

But the two won't talk to each other. I think I'll name them after the two guys in "Grumpy Old Men".

 

[kmowens]

Okay, forget about this. It was a firewall issue. I thought I'd tested simple socket connections on the target box, but the tests actually occured on the same machine. Here's to numbskullery.