Answer the question
In order to leave comments, you need to log in
How to change TIMEOUTconnect parameter in Stunnel?
Hi all.
I have a server running Stunnel.
When called with parameters, it produces;
stunnel -version
stunnel 5.27 on x86_64-unknown-linux-gnu platform
Compiled/running with OpenSSL 1.0.1e 11 Feb 2013
Threading:PTHREAD Sockets:POLL,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI
Global options:
debug = daemon.notice
RNDbytes = 64
RNDfile = /dev/urandom
RNDoverwrite = yes
Service-level options:
ciphers = FIPS (with "fips = yes")
ciphers = HIGH:+3DES:+DH:!aNULL:!SSLv2 (with "fips = no")
debug = notice
logId = sequential
options = NO_SSLv2
options = NO_SSLv3
sessionCacheSize = 1000
sessionCacheTimeout = 300 seconds
stack = 65536 bytes
TIMEOUTbusy = 300 seconds
TIMEOUTclose = 60 seconds
TIMEOUTconnect = 10 seconds
TIMEOUTidle = 43200 seconds
verify = none
Answer the question
In order to leave comments, you need to log in
The issue was resolved by the method of scientific poke. The colleague changed the value in /etc/stunnel/stunnel.conf and /usr/local/etc/stunnel/stunnel.conf, the daemon accepted the parameter. I don’t know if this is a bug, but the value must be changed in both files, if there is no parameter, add it manually.
See here /usr/etc/stunnel/
When starting the daemon, it shows a config file that uses:
# /usr/bin/stunnel
[ ] Clients allowed=512000
[.] stunnel 5.56 on x86_64-pc-linux-gnu platform
[.] Compiled/running with OpenSSL 1.1.1 11 Sep 2018
[.] Threading:PTHREAD Sockets:POLL,IPv6 TLS:ENGINE,FIPS,OCSP,PSK,SNI
[ ] errno: (*__errno_location ())
[.] Reading configuration from file /usr/etc/stunnel/stunnel.conf
...
TIMEOUTconnect = 20
to the file/usr/etc/stunnel/stunnel.conf
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question