The main thing that I'm seeing as the error is: "Could not load DH parameters from stunnel.pem" Below is the entire log file, I am so stumped here. I appreciate any help.
No limit detected for the number of clients make_sockets: s_socket#1: FD=272 allocated (blocking mode) make_sockets: s_socket#2: FD=276 allocated (blocking mode) make_sockets: s_accept: FD=292 allocated (non-blocking mode) stunnel 4.42 on x86-pc-mingw32-gnu platform Compiled/running with OpenSSL 1.0.0d 8 Feb 2011 Threading:WIN32 SSL:ENGINE Auth:none Sockets:SELECT,IPv6 Reading configuration from file stunnel.conf Snagged 64 random bytes from C:/.rnd Wrote 1024 new random bytes to C:/.rnd PRNG seeded successfully Initializing SSL context for service pop3s Certificate: stunnel.pem Certificate loaded Key file: stunnel.pem Private key loaded Could not load DH parameters from stunnel.pem Using hardcoded DH parameters DH initialized with 2048-bit key ECDH initialized with curve prime256v1 SSL options set: 0x01180004 SSL context initialized Initializing SSL context for service imaps Certificate: stunnel.pem Certificate loaded Key file: stunnel.pem Private key loaded Could not load DH parameters from stunnel.pem Using hardcoded DH parameters DH initialized with 2048-bit key ECDH initialized with curve prime256v1 SSL options set: 0x01180004 SSL context initialized Line 91: "socket = l:TCP_NODELAY=1 ": Specified option name is not valid here str_stats: 152 block(s), 11942 byte(s)
Server is down
On Wed, 2011-08-31 11:57:52 -0500, Dayo Akande wrote:
The main thing that I'm seeing as the error is: "Could not load DH parameters from stunnel.pem" Below is the entire log file, I am so stumped here. I appreciate any help.
No limit detected for the number of clients [..] Could not load DH parameters from stunnel.pem Using hardcoded DH parameters DH initialized with 2048-bit key [..] Line 91: "socket = l:TCP_NODELAY=1 ": Specified option name is not valid here str_stats: 152 block(s), 11942 byte(s)
Server is down
Dayo,
I don't think the lack of DH parameters is the problem, as stunnel happily uses hardcoded ones. Instead, I suppose stunnel chokes on line 91 of your stunnel.conf. Maybe 'socket' is used as a service-level option?
HTH,
Ludolf
I see, thank you for the quick responses.
Line 91 specifically reads: socket = l:TCP_NODELAY=1
This has not been changed. Should I perhaps comment this out?
Lines 90-98:
cert = stunnel.pem socket = l:TCP_NODELAY=1 socket = r:TCP_NODELAY=1 debug = 7 output = stunnel.log client = yes [smtpg] accept = 127.0.0.1:25 connect = smtp.gmail.com:465
Thank you,
Dayo Akande
On Wed, Aug 31, 2011 at 1:25 PM, Ludolf Holzheid lholzheid@bihl-wiedemann.de wrote:
On Wed, 2011-08-31 11:57:52 -0500, Dayo Akande wrote:
The main thing that I'm seeing as the error is: "Could not load DH parameters from stunnel.pem" Below is the entire log file, I am so stumped here. I appreciate any help.
No limit detected for the number of clients [..] Could not load DH parameters from stunnel.pem Using hardcoded DH parameters DH initialized with 2048-bit key [..] Line 91: "socket = l:TCP_NODELAY=1 ": Specified option name is not valid here str_stats: 152 block(s), 11942 byte(s)
Server is down
Dayo,
I don't think the lack of DH parameters is the problem, as stunnel happily uses hardcoded ones. Instead, I suppose stunnel chokes on line 91 of your stunnel.conf. Maybe 'socket' is used as a service-level option?
HTH,
Ludolf
--
Ludolf Holzheid Tel: +49 621 339960 Bihl+Wiedemann GmbH Fax: +49 621 3392239 Floßwörthstraße 41 e-mail: lholzheid@bihl-wiedemann.de D-68199 Mannheim, Germany
-
Dayo Akande -
Ludolf Holzheid