![]() ![]() > 2016.05.17 15:57:24 LOG3: SSL_connect: 14090086: error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failedĬAfile should point to a list of trusted certificates. > 2016.05.17 15:57:24 LOG4: CERT: Pre-verification error: self signed certificate in certificate chain > The file includes -BEGIN CERTIFICATE- & -END CERTIFICATE. ![]() > Therefore, I've converted my existing certs file (from my application) into a PEM file. rootclient: /etc/init. To make things more trouble-free, combine the public key and private key certificates into one. Start stunnel Once the configuration is in place we can start the stunnel service. > After further investigation, it became evident that Stunnel should run as client. Double-click on the executable 'stunnel-4. Stunnel-users mailing Tue, 13:08:33 +0000, David Faizulaev wrote: Geschäftsführer: Jochen Bihl, Bernhard Wiedemann Now, stunnel is missing the private key.) "-BEGIN CERTIFICATE-" and "-END CERTIFICATE-", but for This command will gather information about your system and configure Stunnels installation scripts. The default configuration runs Stunnel in a chroot jail. (There also should be a certificate enclosed in "-BEGIN RSA PRIVATE KEY-" and "-END RSA PRIVATE KEY-" Maybe it's not in PEM format, or it does not contain a private key. CONFIGURING STUNNEL FREE> 2016.05.16 19:14:04 LOG3: error queue: 140B0009: error:140B0009:SSL routines:SSL_CTX_use_PrivateKey_file:PEM lib To configure stunnel as a TLS wrapper for CUPS, use the following values: cups accept 632 connect 631 Instead of 632, you can use any free port that you prefer. > Upon initializing Stunnel I get the following error: > I've installed it on to the client machine and configured the client to connect to 127.0.0.1:8449 while the Server to which the client needs to connect is 192.168.220.72:8447 > But I'm having some difficulties configuring the software. > I've found Stunnel as a potential answer to securely moving traffic between two machines. However there is a special case when you wish to have some other program accept incoming connections and launch stunnel, for example with inetd, xinetd, or tcpserver. On Mon, 16:25:04 +0000, David Faizulaev wrote: The most common use of stunnel is to listen on a network port and establish communication with either a new port via the connect option, or a new program via the exec option. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |