I upgraded from stunnel 4.34 to 4.46 (Windows) today, which took much more time than expected.
First, I was surprised to see that my specified service name (via "service =" was ignored), until I eventually found the note in the 4.42 changelog about "Removed support for changing Windows Service name with "service"". This isn't the end of the world (I changed the display name using sc) but it would be very helpful -- and time saving -- if the man page was updated to reflect this change.
A bigger issue I ran into is that because the service can't be renamed, I can have only one stunnel service installed. The only mention of this I found was a reply to a list question saying "Running more than one stunnel service has been obsoleted." What was the motivation behind this change? Though I can specify multiple [service] sections in stunnel.conf, I see no way to control them individually. It has been useful to have separate stunnel (Windows) services installed, which can be stopped and started independently.
Thanks.
John W wrote:
First, I was surprised to see that my specified service name (via "service =" was ignored), until I eventually found the note in the 4.42 changelog about "Removed support for changing Windows Service name with "service"". This isn't the end of the world (I changed the display name using sc) but it would be very helpful -- and time saving -- if the man page was updated to reflect this change.
You're right. This is my fault indeed.
A bigger issue I ran into is that because the service can't be renamed, I can have only one stunnel service installed. The only mention of this I found was a reply to a list question saying "Running more than one stunnel service has been obsoleted." What was the motivation behind this change?
The ultimate goal is to have a separate processes for Windows service and for GUI. Only allowing for a single service simplifies the design. Even simple functions such as shutdown on upgrade are quite complex with multiple services.
Though I can specify multiple [service] sections in stunnel.conf, I see no way to control them individually. It has been useful to have separate stunnel (Windows) services installed, which can be stopped and started independently.
The solution is to change the configuration file and reload it.
Please let me ask you a question similar to the one you asked me: What is the motivation behind your requirement to shutdown services individually?
Best regards, Michal Trojnara
on 2011-11-10 1:22 PM Michal Trojnara said the following: [...]
Though I can specify multiple [service] sections in stunnel.conf, I see no way to control them individually. It has been useful to have separate stunnel (Windows) services installed, which can be stopped and started independently.
The solution is to change the configuration file and reload it.
Please let me ask you a question similar to the one you asked me: What is the motivation behind your requirement to shutdown services individually?
For troubleshooting. I have one stunnel service to provide a few VNC tunnels, and a second service to collect POP3 email securely. My stunnel upgrade was prompted by some problems with the POP3S collection, and in troubleshooting this I wanted to restart this stunnel without affecting the VNC ones.
It just seems "natural" to me that there should be an easy way to control individual tunnels, and under Windows separate services provided it. In principle separate services also prevent problems in one stunnel instance from affecting others, though I don't know that I've ever actually run into this.
Thanks, John
-
John W -
Michal Trojnara