[stunnel-users] Interoperability problems with .net client software
josealf at rocketmail.com
josealf at rocketmail.com
Sat Jun 30 04:36:43 CEST 2012
Not as far as I know. You need to check with the client application developers. Maybe they can use a debugger to trace the program flow and see where and why it fails (assuming they understand the protocols and the tools). The application must be coded to present the certificate, and my guess (just a guess), is that it isn't or is blocking before getting to that point.
From: ProPharma Systems AG - Gregor Bürgisser <g.buergisser at propharma.ch>
Date: Fri, 29 Jun 2012 06:59:14
To: <josealf at rocketmail.com>
Subject: Re: [stunnel-users] Interoperability problems with .net client software
Yes I did. Also the CA used to sign the server cert. All to no avail.
Do you know if there are any (known) interoperability issues between
stunnel and .net applications?
On 06/28/2012 02:05 PM, josealf at rocketmail.com wrote:
> Looks like your client is not presenting the certificate to the stunnel server. Maybe because it does not trust the server certificate? Did you import your stunnel server cert into windows certificate store?
> -----Original Message-----
> From: ProPharma Systems AG - Gregor Bürgisser
> <g.buergisser at propharma.ch>
> Sender: stunnel-users-bounces at stunnel.org
> Date: Thu, 28 Jun 2012 12:48:53
> To:<stunnel-users at stunnel.org>
> Subject: [stunnel-users] Interoperability problems with .net client software
> Hi all,
> I'm using stunnel 4.53 under Linux to secure a service. There are two
> different clients connecting to this service: My own client, also Linux
> based and using libcurl and another (third party!) client being
> developed using Microsoft .net stuff.
> Of course with my own client all works well. But we are not able to get
> the Microsoft client running. stunnel keeps on telling:
> SSL_accept: 140890C7: error:140890C7:SSL
> routines:SSL3_GET_CLIENT_CERTIFICATE:peer did not return a certificate
> We have tried diffierent things... I will outline them here if you think
> it is helpful (in short: tried using certificates generated on the
> Microsoft side, then tried using certificates created on the Linux side).
> If "verify" ist set to 0 or 1 it works (of course) but with a higher
> value the above message is logged.
> Are there any known pitfalls, problems or whatsoever when using stunnel
> with a .net client?
> Any advice would be appreciated!
> stunnel-users mailing list
> stunnel-users at stunnel.org
More information about the stunnel-users