Thanks Michal,
Personally, I only need to examine the ST GUI if there is a problem or to confirm a configuration change. Manually starting the GUI or creating a scheduled task which starts the GUI at logon is easy enough for the end user to accomplish, IMHO.
I mostly use ST on Windows servers, so the most important thing to me is having ST start reliably, as a service, and function whether a user has logged on or not.
Thank you for all of your hard work and for providing this indispensable tool.
On 09.25.2014 06:26, Michal Trojnara wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Guys,
The proper solution is to move the GUI to a separate process.
There will be two separate logical components:
- Network server running as an NT service or a user process.
- GUI client always running as the current user.
The stunnel process executed by the current user will first check whether an existing network server (possibly running as NT service) is already started:
- On success, it will communicate with the server over a named pipe.
- On failure, it will start a new network server as the current user.
This feature is already on my TODO list http://www.stunnel.org/sdf_todo.html waiting for a sponsor, or for me to have some spare time...
Mike -----BEGIN PGP SIGNATURE----- Version: GnuPG v1
iEYEARECAAYFAlQkGB8ACgkQ/NU+nXTHMtGeDQCfRTEPnU74ahtQVFHC4La6EWew pE8AoN33l1bUj3qdivRKseTFRdBqd87H =SbCw -----END PGP SIGNATURE----- _______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users