tunnel-users] Help in setting stunnel in server mode to over
come TLSV2 compatibility
Jothish,
1. You are using a very outdated version of OpenSSL (openssl 0.9.8 is EOL). I
suggest you use a newer, supported version.
2. On a DOS Window, try this:
openssl dhparam -rand randfile1;randfile2;randfile
Sent: Thursday, November 24, 2016 6:45 AM
Subject: RE: [stunnel-users] Help in setting stunnel in server mode to over
come TLSV2 compatibility
#yiv9373448809 #yiv9373448809 -- _filtered #yiv9373448809
{font-family:Wingdings;panose-1:5 0 0 0 0 0 0 0 0 0;} _filtered #yiv9373448809
{panose-1:2 4
]
Sent: Thursday, November 24, 2016 4:36 PM
To: Chokkalingam, Jothish <jothish.chokkalin...@accenture.com>
Cc: cbro...@cbcs-usa.com; stunnel-users@stunnel.org
Subject: Re: [stunnel-users] Help in setting stunnel in server mode to over
come TLSV2 compatibility
Can you please elaborate? If you wan
lin...@accenture.com>
> Cc: cbro...@cbcs-usa.com; stunnel-users@stunnel.org
> Subject: Re: [stunnel-users] Help in setting stunnel in server mode to over
> come TLSV2 compatibility
>
> Jothish,
>
> Stunnel in server mode is what you need, with 99.9% confidence.
>
> When
sa.com; stunnel-users@stunnel.org
Subject: Re: [stunnel-users] Help in setting stunnel in server mode to over
come TLSV2 compatibility
Jothish,
Stunnel in server mode is what you need, with 99.9% confidence.
When you write:
[https]
Accept=443
Connect=local host:80
Client=no
Stunnnel will expe
There are other tools for performing port forwarding with less overhead
(I believe tappipe is one), although I make use stunnel to do this
extensively.
In order forward a secure connection from one port to another is a two
step process with stunnel:
A sample configuration segment would be:
Hi, there.
I'm no stunnel expert, but here's my $0.05 (we have no pennies in Canada
anymore ;-) ):
- I would try including the key as well as the cert in your stunnel config
- I would enable debug on the openssl s_client call to see if it will indicate
why it is reseting. Same with your SFDC
HI all,
There is a problem we have currently connecting tibco client to SFDC sever via
TLS v1.2 and that's solved by using stunnel in client mode. And the
communication from SFDC client to tibco server applications w.r.t TLS V1.2 I am
unable to solve using stunnel. Below is the configuration
