Hi Hamid,
If I were in your position, I would not try to debug two pieces of
complex code at the same time.
I would recommend first trying to get the Windows ssl/tls calls
working in a simple C program, completely separated from Qpid code.
When that is working with your server and client certific
P.S. I have also tried it with the host name and get the following error;
2012-01-25 18:08:09 notice SSL negotiation failed to :10170:
The target principal name is incorrect.
Best Regards,
- Hamid
--
View this message in context:
http://qpid.2158936.n2.nabble.com/warning-Connect-failed-tp722998
*Hi Jakub,*
Thank you for explaining the chrome related issue. Basically, my application
will run as a console application rather like a service but I will discuss
with the server/broker side regarding the CA and Trusted Peer thing you
mentioned.
*Hi Cliff, *
Unfortunately, the server (broker)
