Setup an incoming encrypted link from a windows telnet session to openvms.
-----Original Message----- From: stunnel-users [mailto:stunnel-users-bounces@stunnel.org] On Behalf Of Carter Browne Sent: Wednesday, April 08, 2015 12:00 PM To: stunnel-users@stunnel.org Subject: Re: [stunnel-users] openvms and stunnel
Paul,
What are you trying to do:
Set up an incoming encrypted link to an outgoing unencrypted link? Set up an incoming unencrypted link to an outgoing encrypted link? Something else?
Carter
On 4/8/2015 11:49 AM, Coviello, Paul wrote:
Let me see so I need to do the following.
connect = 192.168.0.1:993 connect = 192.168.20.140:993 connect = 192.168.xx.xxx:993 connect = 192.168.xx.xxy:993
Thanks Paul
-----Original Message----- From: stunnel-users [mailto:stunnel-users-bounces@stunnel.org] On Behalf Of Ludolf Holzheid Sent: Wednesday, April 08, 2015 11:35 AM To: stunnel-users@stunnel.org Subject: Re: [stunnel-users] openvms and stunnel
On Wed, 2015-04-08 11:18:43 -0400, Coviello, Paul wrote:
Hello
I'm trying to setup stunnel 4.20 yes it is an old version but the only one on HP's website for VMS.
I need a little help in the conf files.
Since I will be using telnet, do I need to put in each machines ip address that will be connecting? So in the example below do I create a listing of connects?
[telnet] accept = 999 connect = 192.168.0.1:993
Paul,
the configuration above makes stunnel listen on local port 999, accepting connections from all IP addresses and forwards the traffic to port 993 of the box with IP address 192.168.0.1.
Depending on the 'client = ...' statement, stunnel expects the traffic at port 999 to be encrypted (server mode, client = no, default), or at port 993 (client mode, client = yes).
Any access control may be implemented via libwrap and (in server mode) via restriction of the accepted certificates.
HTH,
Ludolf