> I received no information on this bug for more than one year, I assume >that it was fixed in higher release of stunnel. If this is not the case, >please >reopen the bug.
Sorry for not providing more info sooner. Yes, stunnel4 hanged with that configuration file, but now it does not any more: instead, it spits an error because no service is configured. When I configure a service, it starts in the background, as it should. I did not check that it indeed works, because I do not use stunnel any more. Anyway, yes, the bug is correctly closed. Thank you for your work. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
