Hi all, One for any gurus on this list (I know you are out there) I am attempting to set up a secure pop server (pop3s) on a RH7.2 box. I have followed all the instructions (not that they are easy to find), creating a self-signed certificate including both private key and certificate in the same file, at /usr/share/ssl/certs/imapd.pem
The correct hole is punched in the firewall config: 995 The imapd package, allegedly, comes preconfigured to use a certificate at the above-mentioned location in secure mode. So, in theory, that should be fine. On to the testing phase: []# openssl s_client -connect localhost:995 -prexit (*) gives the following output CONNECTED(00000003) write:errno=104 * tested both with localhost and the full machine name, with absolutely no difference. So, I tried it with []# openssl s_client -connect localhost:995 -prexit getting a little more info.... CONNECTED(00000003) write:errno=104 --- no peer certificate available --- No client certificate CA names sent --- SSL handshake has read 0 bytes and written 124 bytes --- New, (NONE), Cipher is (NONE) --- It would appear that this is an openssl error, though just where it originates from, I am not sure. It could be that ipopd isn't automatically compiled with SSL support. It could be that the key file location or name is incorrectly documented. It could be something totally different. Has anyone on the list come across a similar problem, and more to the point managed to get it working? Thanks - Rick ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
