stunnel-users

stunnel-users@stunnel.org

5 participants
3293 discussions

RE: [stunnel-users] Re: Can stunnel do this?
by Matteo D'Amato 07 Mar '06

07 Mar '06

Here is what I'm getting Insude stunnel.conf file: cert=/usr/local/etc/stunnel/stunnel.pem cafile=/usr/local/etc/stunnel/stunnel.pem output=/var/log/stunnel.log client=yes debug=7 [1440] accept=10.10.10.2:1440 connect=192.168.19.50:1078 Launched using: stunnel /etc/stunnel/stunnel.conf -p /usr/local/etc/stunnel/stunnel.pem Log file: 2006.03.07 08:30:01 LOG5[13209:0]: Received signal 15; terminating 2006.03.07 08:30:01 LOG7[13209:0]: removing pid file /usr/local/var/stunnel/stunnel.pid 2006.03.07 08:30:20 LOG5[13219:1]: stunnel 4.14 on i686-pc-linux-gnu UCONTEXT+POLL+IPv4+LIBWRAP with OpenSSL 0.9.7a Feb 19 2003 2006.03.07 08:30:20 LOG7[13219:1]: Snagged 64 random bytes from /root/.rnd 2006.03.07 08:30:20 LOG7[13219:1]: Wrote 1024 new random bytes to /root/.rnd 2006.03.07 08:30:20 LOG7[13219:1]: RAND_status claims sufficient entropy for the PRNG 2006.03.07 08:30:20 LOG6[13219:1]: PRNG seeded successfully 2006.03.07 08:30:20 LOG7[13219:1]: Certificate: /usr/local/etc/stunnel/stunnel.pem 2006.03.07 08:30:20 LOG7[13219:1]: Key file: /usr/local/etc/stunnel/stunnel.pem 2006.03.07 08:30:20 LOG6[13219:1]: file ulimit = 1024 (can be changed with 'ulimit -n') 2006.03.07 08:30:20 LOG6[13219:1]: poll() used - no FD_SETSIZE limit for file descriptors 2006.03.07 08:30:20 LOG5[13219:1]: 500 clients allowed 2006.03.07 08:30:20 LOG7[13219:1]: FD 4 in non-blocking mode 2006.03.07 08:30:20 LOG7[13219:1]: FD 5 in non-blocking mode 2006.03.07 08:30:20 LOG7[13219:1]: FD 6 in non-blocking mode 2006.03.07 08:30:20 LOG7[13219:1]: SO_REUSEADDR option set on accept socket 2006.03.07 08:30:20 LOG7[13219:1]: 1440 bound to 10.10.10.2:1440 2006.03.07 08:30:20 LOG7[13220:1]: Created pid file /usr/local/var/stunnel/stunnel.pid 2006.03.07 08:30:20 LOG7[13220:0]: Waiting -1 second(s) for 2 file descriptor(s) 2006.03.07 08:31:46 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:46 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->(IN) 2006.03.07 08:31:46 LOG7[13220:1]: 1440 accepted FD=7 from 10.10.10.100:1049 2006.03.07 08:31:46 LOG7[13220:1]: Creating a new context 2006.03.07 08:31:46 LOG7[13220:1]: Context 2 created 2006.03.07 08:31:46 LOG7[13220:2]: Context swap: 1 -> 2 2006.03.07 08:31:46 LOG7[13220:2]: 1440 started 2006.03.07 08:31:46 LOG7[13220:2]: FD 7 in non-blocking mode 2006.03.07 08:31:46 LOG7[13220:2]: FD 8 in non-blocking mode 2006.03.07 08:31:46 LOG7[13220:2]: FD 9 in non-blocking mode 2006.03.07 08:31:46 LOG7[13221:0]: Waiting 300 second(s) for 3 file descriptor(s) 2006.03.07 08:31:46 LOG7[13221:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:46 LOG7[13221:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:31:46 LOG7[13221:0]: CONTEXT 2, FD=9, (OUT)->(OUT) 2006.03.07 08:31:46 LOG7[13220:0]: Waiting 300 second(s) for 3 file descriptor(s) 2006.03.07 08:31:46 LOG7[13220:0]: Cleaning up the signal pipe 2006.03.07 08:31:46 LOG6[13220:0]: Child process 13221 finished with code 0 2006.03.07 08:31:46 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:46 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:31:46 LOG7[13220:0]: CONTEXT 2, FD=8, (IN)->(INHUP) 2006.03.07 08:31:46 LOG7[13220:2]: Connection from 10.10.10.100:1049 permitted by libwrap 2006.03.07 08:31:46 LOG5[13220:2]: 1440 connected from 10.10.10.100:1049 2006.03.07 08:31:46 LOG7[13220:2]: FD 8 in non-blocking mode 2006.03.07 08:31:46 LOG7[13220:2]: 1440 connecting 192.168.19.50:1078 2006.03.07 08:31:46 LOG7[13220:2]: connect_wait: waiting 10 seconds 2006.03.07 08:31:46 LOG7[13220:0]: Waiting 10 second(s) for 3 file descriptor(s) 2006.03.07 08:31:46 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:46 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:31:46 LOG7[13220:0]: CONTEXT 2, FD=8, (INOUT)->(OUT) 2006.03.07 08:31:46 LOG7[13220:2]: connect_wait: connected 2006.03.07 08:31:46 LOG7[13220:2]: Remote FD=8 initialized 2006.03.07 08:31:46 LOG7[13220:2]: SSL state (connect): before/connect initialization 2006.03.07 08:31:46 LOG7[13220:2]: SSL state (connect): SSLv3 write client hello A 2006.03.07 08:31:46 LOG7[13220:0]: Waiting 300 second(s) for 3 file descriptor(s) 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->(IN) 2006.03.07 08:31:47 LOG7[13220:1]: CONTEXT 2, FD=8, (IN)->() 2006.03.07 08:31:47 LOG7[13220:1]: Context swap: 2 -> 1 2006.03.07 08:31:47 LOG7[13220:1]: Current context: 1 2006.03.07 08:31:47 LOG7[13220:1]: 1440 accepted FD=9 from 10.10.10.100:1050 2006.03.07 08:31:47 LOG7[13220:1]: Creating a new context 2006.03.07 08:31:47 LOG7[13220:1]: Context 3 created 2006.03.07 08:31:47 LOG7[13220:3]: Context swap: 1 -> 3 2006.03.07 08:31:47 LOG7[13220:3]: 1440 started 2006.03.07 08:31:47 LOG7[13220:3]: FD 9 in non-blocking mode 2006.03.07 08:31:47 LOG7[13220:3]: FD 10 in non-blocking mode 2006.03.07 08:31:47 LOG7[13220:3]: FD 11 in non-blocking mode 2006.03.07 08:31:47 LOG7[13222:0]: Waiting 299 second(s) for 4 file descriptor(s) 2006.03.07 08:31:47 LOG7[13222:0]: CONTEXT 2, FD=8, (IN)->() 2006.03.07 08:31:47 LOG7[13222:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:47 LOG7[13222:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:31:47 LOG7[13222:0]: CONTEXT 3, FD=11, (OUT)->(OUT) 2006.03.07 08:31:47 LOG7[13220:0]: Waiting 299 second(s) for 4 file descriptor(s) 2006.03.07 08:31:47 LOG7[13220:0]: Cleaning up the signal pipe 2006.03.07 08:31:47 LOG6[13220:0]: Child process 13222 finished with code 0 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 2, FD=8, (IN)->() 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 3, FD=10, (IN)->(INHUP) 2006.03.07 08:31:47 LOG7[13220:3]: Connection from 10.10.10.100:1050 permitted by libwrap 2006.03.07 08:31:47 LOG5[13220:3]: 1440 connected from 10.10.10.100:1050 2006.03.07 08:31:47 LOG7[13220:3]: FD 10 in non-blocking mode 2006.03.07 08:31:47 LOG7[13220:3]: 1440 connecting 192.168.19.50:1078 2006.03.07 08:31:47 LOG7[13220:3]: connect_wait: waiting 10 seconds 2006.03.07 08:31:47 LOG7[13220:0]: Waiting 10 second(s) for 4 file descriptor(s) 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 2, FD=8, (IN)->() 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 3, FD=10, (INOUT)->(OUT) 2006.03.07 08:31:47 LOG7[13220:3]: connect_wait: connected 2006.03.07 08:31:47 LOG7[13220:3]: Remote FD=10 initialized 2006.03.07 08:31:47 LOG7[13220:3]: SSL state (connect): before/connect initialization 2006.03.07 08:31:47 LOG7[13220:3]: SSL state (connect): SSLv3 write client hello A 2006.03.07 08:31:47 LOG7[13220:0]: Waiting 299 second(s) for 4 file descriptor(s) 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 2, FD=8, (IN)->(IN) 2006.03.07 08:31:47 LOG7[13220:2]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:47 LOG7[13220:2]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:31:47 LOG7[13220:2]: CONTEXT 3, FD=10, (IN)->() 2006.03.07 08:31:47 LOG7[13220:2]: Context swap: 3 -> 2 2006.03.07 08:31:47 LOG7[13220:2]: Current context: 2 2006.03.07 08:31:47 LOG7[13220:0]: Waiting 300 second(s) for 4 file descriptor(s) 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:31:47 LOG7[13220:0]: CONTEXT 3, FD=10, (IN)->(IN) 2006.03.07 08:31:47 LOG7[13220:3]: CONTEXT 2, FD=8, (IN)->() 2006.03.07 08:31:47 LOG7[13220:3]: Context swap: 2 -> 3 2006.03.07 08:31:47 LOG7[13220:3]: Current context: 3 2006.03.07 08:31:47 LOG7[13220:0]: Waiting 300 second(s) for 4 file descriptor(s) 2006.03.07 08:32:02 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:32:02 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:32:02 LOG7[13220:0]: CONTEXT 2, FD=8, (IN)->(IN) 2006.03.07 08:32:02 LOG7[13220:2]: CONTEXT 3, FD=10, (IN)->() 2006.03.07 08:32:02 LOG7[13220:2]: Context swap: 3 -> 2 2006.03.07 08:32:02 LOG7[13220:2]: Current context: 2 2006.03.07 08:32:02 LOG7[13220:0]: Waiting 285 second(s) for 4 file descriptor(s) 2006.03.07 08:32:02 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:32:02 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:32:02 LOG7[13220:0]: CONTEXT 3, FD=10, (IN)->(IN) 2006.03.07 08:32:02 LOG7[13220:3]: CONTEXT 2, FD=8, (IN)->() 2006.03.07 08:32:02 LOG7[13220:3]: Context swap: 2 -> 3 2006.03.07 08:32:02 LOG7[13220:3]: Current context: 3 2006.03.07 08:32:02 LOG7[13220:0]: Waiting 300 second(s) for 4 file descriptor(s) 2006.03.07 08:32:17 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:32:17 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:32:17 LOG7[13220:0]: CONTEXT 2, FD=8, (IN)->(IN) 2006.03.07 08:32:17 LOG7[13220:2]: CONTEXT 3, FD=10, (IN)->() 2006.03.07 08:32:17 LOG7[13220:2]: Context swap: 3 -> 2 2006.03.07 08:32:17 LOG7[13220:2]: Current context: 2 2006.03.07 08:32:17 LOG7[13220:2]: SSL alert (write): fatal: handshake failure 2006.03.07 08:32:17 LOG3[13220:2]: SSL_connect: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number 2006.03.07 08:32:17 LOG7[13220:2]: 1440 finished (1 left) 2006.03.07 08:32:17 LOG5[13220:2]: stack_info: size=65536, current=4208 (6%), maximum=4208 (6%) 2006.03.07 08:32:17 LOG7[13220:2]: Context 2 closed 2006.03.07 08:32:17 LOG7[13220:0]: Waiting 285 second(s) for 3 file descriptor(s) 2006.03.07 08:32:17 LOG7[13220:0]: CONTEXT 1, FD=4, (IN)->() 2006.03.07 08:32:17 LOG7[13220:0]: CONTEXT 1, FD=6, (IN)->() 2006.03.07 08:32:17 LOG7[13220:0]: CONTEXT 3, FD=10, (IN)->(IN) 2006.03.07 08:32:17 LOG7[13220:3]: Context set: 2 (dropped) -> 3 2006.03.07 08:32:17 LOG7[13220:3]: Current context: 3 2006.03.07 08:32:17 LOG7[13220:3]: Releasing context 2 2006.03.07 08:32:17 LOG7[13220:3]: SSL alert (write): fatal: handshake failure 2006.03.07 08:32:17 LOG3[13220:3]: SSL_connect: 1408F10B: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number 2006.03.07 08:32:17 LOG7[13220:3]: 1440 finished (0 left) 2006.03.07 08:32:17 LOG5[13220:3]: stack_info: size=65536, current=4208 (6%), maximum=4208 (6%) 2006.03.07 08:32:17 LOG7[13220:3]: Context 3 closed 2006.03.07 08:32:17 LOG7[13220:0]: Waiting -1 second(s) for 2 file descriptor(s) --Matteo D'Amato

1 0

RE: [stunnel-users] Re: Can stunnel do this?
by Kevin A. McGrail 07 Mar '06

07 Mar '06

This sounds like exactly what stunnel does. You want to have host A talk to Server A via SSL so you run stunneld on it. Then it will redirect that connection to server B via non-SSL. What protocol are we talking about here? Let's assume it's https: On Server A, setup stunnel with a conf file with these lines (as well as many others surely) [https] accept = 443 connect = serverb.smartbox.ca:80 Then your host connects to server a, negotiates SSL and the information is sent to the other server. I think your biggest issue is going to be the certificate on Server A so that the Host connects to the Server without certificate issues. Sincerely, Kevin A. McGrail aka KAM > -----Original Message----- > From: stunnel-users-bounces(a)mirt.net > [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Matteo D'Amato > Sent: Monday, March 06, 2006 7:20 PM > To: stunnel-users(a)mirt.net > Subject: RE: [stunnel-users] Re: Can stunnel do this? > > Stunnel can only be installed on Server A > > > > --Matteo D'Amato > > -----Original Message----- > From: stunnel-users-bounces(a)mirt.net > [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Matteo D'Amato > Sent: Monday, March 06, 2006 5:58 PM > To: stunnel-users(a)mirt.net > Subject: [stunnel-users] Re: Can stunnel do this? > > Hi, > Can stunnel do this > > > Host A ---------> Server A ---------> Server B > SSL unencrypted > > This looks like the opposite of what stunnel does. I have a > host that speaks SSL that needs to talk to a server that does > not and the host must always initiate the connection. Any > ideas if this can be done with stunnel or is there another > way to do this. Thanks

1 0

RE: [stunnel-users] Re: Can stunnel do this?
by Matteo D'Amato 07 Mar '06

07 Mar '06

Stunnel can only be installed on Server A --Matteo D'Amato -----Original Message----- From: stunnel-users-bounces(a)mirt.net [mailto:stunnel-users-bounces@mirt.net] On Behalf Of Matteo D'Amato Sent: Monday, March 06, 2006 5:58 PM To: stunnel-users(a)mirt.net Subject: [stunnel-users] Re: Can stunnel do this? Hi, Can stunnel do this Host A ---------> Server A ---------> Server B SSL unencrypted This looks like the opposite of what stunnel does. I have a host that speaks SSL that needs to talk to a server that does not and the host must always initiate the connection. Any ideas if this can be done with stunnel or is there another way to do this. Thanks -- Matteo D'Amato Smartbox Equipment Inc _______________________________________________ stunnel-users mailing list stunnel-users(a)mirt.net http://stunnel.mirt.net/mailman/listinfo/stunnel-users

1 0

Re: Can stunnel do this?
by Matteo D'Amato 06 Mar '06

06 Mar '06

Hi, Can stunnel do this Host A ---------> Server A ---------> Server B SSL unencrypted This looks like the opposite of what stunnel does. I have a host that speaks SSL that needs to talk to a server that does not and the host must always initiate the connection. Any ideas if this can be done with stunnel or is there another way to do this. Thanks -- Matteo D'Amato Smartbox Equipment Inc

1 0

configure problem in 4.14
by MeeAGhost 06 Mar '06

06 Mar '06

Whether --enable-dh is defined or not the stunnel created certificates created during make-install will include DH support. This is because the USE_DH variable in tools/Makefile is undefined which in turn causes the test portion of the install-data-local section of the tools/Makefile below to fail test $(USE_DH) -eq 0 || $(openssl) gendh $$RND 512 >> stunnel.pem; \ $(openssl) x509 -subject -dates -fingerprint -noout -in stunnel.pem; \ ${INSTALL} -m 600 stunnel.pem $(DESTDIR)$(confdir)/stunnel.pem; \ rm stunnel.pem; \ The test fails with this error message "/bin/bash: test: -eq: unary operator expected" since USE_DH is empty (undefined). I looked at the dh section of the configure script and it appears USE_DH is being set to 1 when --enable-dh is defined. However, USE_DH=1 is only in the DEFS section of tools/Makefile and not actually setting the value of USE_DH variable. I read in the change notes (from several years ago) that dh was disabled by default. I have been running stunnel for the past 3-4 years but have since I initially installed it back then I have been upgrading and therefore the above section of the tools\Makefile was skipped since I already had certificates defined. I went to install on a new box today and found the above 'problem'. So I am not sure how long this has been like this. Before I tried to figure out what is "wrong" I wanted to see if others have noticed this. I have seen this on Solaris 9 and in the cygwin 1.5.19.

2 1

tappipe 1.02 (stable!) released
by Michal Trojnara 03 Mar '06

03 Mar '06

Dear Users, The stable version of my VPN for stunnel/Linux is ready for download here: ftp://ftp.mirt.net/tappipe/ AFAIK it's the shortest (only 356 lines in C language) and probably one of the easiest to setup VPNs ever. Here is the ChangeLog entry: * version 1.02 2006.03.03, status: functional, stable - retransmission rate limiting algoritm improved - some minor bugfixes Could someone contribute a manual page? 8-) Best regards, Mike

1 0

Zombie problem with stunnel-4.11
by Ole Husgaard 01 Mar '06

01 Mar '06

Hi, I am trying to set up stunnel to be invoked from xinetd.d to secure pop3 access, and I'm having problems with zombie processes. It looks like stunnel does not clean up after the pop3 session: 31679 ? Ss 0:00 xinetd -stayalive -reuse -pidfile /var/run/xinetd.pid 32049 ? Ss 0:00 \_ stunnel /etc/pop3s/stunnel.cnf 32050 ? Z 0:00 \_ [ipop3d] <defunct> The contents of my stunnel.cnf file is: CAfile = /var/www/html/ca-cert.crt CRLfile = /var/www/html/ca-crl.crl cert = /etc/pop3s/pop3s.cert key = /etc/pop3s/pop3s.key verify = 2 exec = /usr/sbin/ipop3d execargs = ipop3d I use a non-standard port 997 for the service, so I have the line pop3s-eXerp 997/tcp in my /etc/services file. The xinetd configuration file for the service is: service pop3s-eXerp { disable = no socket_type = stream wait = no user = root server = /usr/sbin/stunnel server_args = /etc/pop3s/stunnel.cnf log_on_success += USERID log_on_failure += USERID } I have searched the net, but have not seen anybody else who have had this problem. Does anybody have an idea of what is causing this problem, or what I can do to work around it? Best Regards, Ole Husgaard.

2 1

Client setup
by Ting 21 Feb '06

21 Feb '06

Hello all, Wonder if anybody could advise. I have a client tn3270 application running on Solaris 2.8. Currently, it is using clear text to communicate with tn3270 server. Now, I need to run tn3270 with SSL. If I install stunnel in the Solaris 2.8 box to act as a wrapper. 1. Do I run the stunnel as a client only ? Is the command: stunnel -c -d <port1> -r <tn3270server>:<port2> a. Is port1 the original port where client tn3270 application sends to server ? b. Is port2 the same as port1 ? c. Alternatively, am I supposed to change the client tn3270 application to direct the data to a new port X, then port1 = X, while port2 is the port where the server is listening on. Thank you in advance. Warm Regards, TW --------------------------------- Do you Yahoo!? Yahoo! Movies - Search movie info and celeb profiles and photos.

2 1

Choosing local 'source' IP?
by Don Werve 20 Feb '06

20 Feb '06

Ok, so here's the problem: I've got stunnel handling SSL for a web-based service that is otherwise too stupid to be able to talk https. Unfortunately, I need to set up a redirection rule inside this service that bounces people back to the https:// page if they try to come in over http. Since said service isn't managing its own SSL, I have no solid way of determining which connections are wrappered by stunnel and which connections come in over the wire, and if I bounce stunnel connections, I end up in an infinite loop. Fortunately, all stunnel connections give a REMOTE_IP of the second ethernet adapter of the host system, which is good. My question is, how do I configure stunnel to 'force' this behavior? E.g., I want to explicitly specify in stunnel.conf 'Connect to the service for which you are acting as a wrapper from *this* IP/interface'. I've tried the 'local = ' option and setting socket flags for 'l' and 'r', and while they don't break anything, I can't use them to force a connection from any other adapter, so I don't think they are doing what I need. This wouldn't be an issue, either, except I don't know how stunnel determines this, and I don't want to (at some point in the future) have things 'magically change' (read: break horribly). Thanks-in-advance! -- Don Werve <donw(a)iradeon.net> Chief Systems Administrator / Systems Architect

2 1

RE: question about stunnel setup
by Anthony Cicalla 15 Feb '06

15 Feb '06

Encrypting traffic to a remote syslog-ng server including SSL peer authentication 1. Install stunnel and syslog-ng on all machines. 2. Create certificates for all machines. On RedHat 9 and similar machines, you can do the following as root: # cd /etc/pki/tls/certs # make syslog-ng-server.pem # make syslog-ng-client.pem 3. Place copies of syslog-ng-server.pem on all machines in /etc/stunnel with one important alteration. The clients only need the certificate section of syslog-ng-server.pem. In other words, remove the private key section from syslog-ng-server.pem on all clients. Place every client's syslog-ng-client.pem in /etc/stunnel. For server, create a special syslog-ng-client.pem containing the certificate sections for all clients and place in /etc/stunnel. In other words, remove the private key sections from all syslog-ng-client.pem files and concatenate what is left to create server's special syslog-ng-client.pem. Ok my question is from above it says to create one syslog-ng-client.pem file per client. 1)Do the names for each of these need to remain syslog-ng-client.pem or can they have names that reflect the host that they are on? 2) if they all need to keep that name do just move the client file to one client/host and then delete it from the server then move on to create the next?

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

stunnel-users