Guenter Palm wrote: > (... snip ...) > > > I did a fresh install based on toaster 0.8.7 on a new machine with SuSE 10.0 a few days ago. > Everything worked fine, and all tests went well. > Then I made an online-update of the OS - with the result that my SuSE installation got messed up by a certain part of the update and I > > had to reinstall the OS. > > (... snip ...) > > Everything went fine, but when I tested SSL/TLS connection for pop, like described in the toaster: > > #openssl s_client -connect localhost:995 > CONNECTED(00000003) > depth=0 /C=DE/ST=...(the rest of my cert-data)... > verify error:num=18:self signed certificate verify return:1 depth=0 /C=DE/ST=...(the rest of my cert-data)... > verify return:1 > > (whatever input I make here - it's just ignored) > > I can't remember how it was with the first install, but I'm sure I didn't see any of this. > The thing is, that I don't know where to go from there. If I stop the whole thing with CTRL-C, > an stunnel process keeps running at 99.9% > CPU usage. > > (... snip ...)
Hi again, just to let you know: problem solved - update of stunnel did the trick! I hadn't bothered to run any updates after installing the new system because that one part (APM/ACPI related) crashed my machine the first time. The original SuSE 10 distro comes with stunnel v4.10-3, which has a bug. The update to v4.10-3.2 says: "This update fixes a threading problem with stunnel 4.10 which could lead to a hang or segfault upon connection" Yes, that was exactly what happend here - but now it's running fine. Just one - maybe silly - question though: should 'domain.com' in stunnel.conf be replaced by the name of my domain (or even the FQDN of the server)? Regards, Guenter
