Thanks for the info...I applied the proposed patch and now I get the following fatal SSL error
XML::Stream: new: hostname = (xxx)
XML::Stream: SetCallBacks: tag(node) func(CODE(0x37f1608))
XMPP::Conn: xmppCallbackInit: start
XMPP::Conn: SetCallBacks: tag(message) func(CODE(0x37f1860))
XMPP::Conn: SetCallBacks: tag(presence) func(CODE(0x37f17a0))
XMPP::Conn: SetCallBacks: tag(iq) func(CODE(0x37f1680))
XMPP::Conn: SetPresenceCallBacks: type(subscribe) func(CODE(0x37f1788)
+)
XMPP::Conn: SetPresenceCallBacks: type(subscribed) func(CODE(0x37f1ae8
+))
XMPP::Conn: SetPresenceCallBacks: type(unsubscribe) func(CODE(0x37f1a2
+8))
XMPP::Conn: SetPresenceCallBacks: type(unsubscribed) func(CODE(0x37f1b
+a8))
XMPP::Conn: SetDirectXPathCallBacks: xpath(/[@xmlns="urn:ietf:params:x
+ml:ns:xmpp-tls"]) func(CODE(0x37f1ad0))
XMPP::Conn: SetDirectXPathCallBacks: xpath(/[@xmlns="urn:ietf:params:x
+ml:ns:xmpp-sasl"]) func(CODE(0x37f1cb0))
XMPP::Conn: xmppCallbackInit: stop
XMPP::Conn: SetCallBacks: tag(iq) func(CODE(0x37efb88))
XMPP::Conn: SetCallBacks: tag(presence) func(CODE(0x37eff90))
XMPP::Conn: SetCallBacks: tag(message) func(CODE(0x37ef6c0))
XMPP::Conn: Connect: host(hostpart:5222) namespace(jabber:client)
XMPP::Conn: Connect: timeout(10)
XML::Stream: Connect: type(tcpip)
XML::Stream: Connect: Got a connection
XML::Stream: Send: (<?xml version='1.0'?><stream:stream version='1.0'
+xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
+ to='hostpart' from='xxx' xml:lang='en' >)
XML::Stream: Read: buff(<?xml version='1.0' encoding='utf-8'?><stream:
+stream xmlns:stream="http://etherx.jabber.org/streams" from="hostpart
+" id="078414e9-d180-43c3-bab9-6ea07a1ae870" version="1.0" xmlns="jabb
+er:client">)
XML::Stream: Read: buff(<stream:features xmlns:stream="http://etherx.j
+abber.org/streams"><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/
+></stream:features>)
XMPP::Conn: Connect: connection made
XML::Stream: SetCallBacks: tag(node) func(CODE(0x37f1728))
XML::Stream: Send: (<starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/
+>)
XML::Stream: Read: buff(<proceed xmlns="urn:ietf:params:xml:ns:xmpp-tl
+s"/>)
XML::Stream: TLSClientProceed: Convert normal socket to SSL
XML::Stream: TLSClientProceed: sock(IO::Socket::INET=GLOB(0x37f1e00))
XML::Stream: LoadSSL: Load the IO::Socket::SSL module
XML::Stream: LoadSSL: Success
XML::Stream: TLSClientProceed: Error during start_SSL: SSL connect att
+empt failed with unknown error error:14090086:SSL routines:SSL3_GET_S
+ERVER_CERTIFICATE:certificate verify failed
So, is there any way to resolve this SSL error?
I have a certificate file that I point to with the command below (certificate was taken from the directory of a Windows Pidgin client install that connects to the server with no problems. (Please note that the code I am running is on a windows machine running strawberry Perl))
my $path='C:\Program Files (x86)\Pidgin\ca-certs';
my $status = $Connection->Connect(hostname=>$server,
port=>$port,
connectiontype => 'tcpip',
tls => 1,
ssl_ca_path =>$path);
Where all the variables are declared beforehand
However I have noticed that if I change the folder in the $path variable to another location that exists on my windows system I get the same SSL error so is there a fundamental problem with my Pidgin certificate?
Any further help much appreciated as have now been looking at this for a while with zero progress!
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.