On Sun, Sep 21, 2003 at 04:41:29PM +0200, Andreas Aardal Hanssen ([EMAIL PROTECTED]) wrote: > > The original package gives you the option to go "make cert", and that > creates a PEM encoded file which contains a self-signed certificate and a > private key. This is the file that Binc IMAP wants. > > > The README says: > > To create a self signed SSL certificate, run "make cert". >
Right, and I was unable to find any Makefile in any of my ssl directories. The only script I found that made certs was CA.pl. I'll use it to remake yet another self signed cert in the intereste of thoroughness. > The FAQ says: > > http://www.bincimap.org/bincimap-faq.html#q13 > > "SSL in Binc IMAP is quite simple to set up. First you need a PEM > encoded private key and certificate file. In some distributions, > you can generate this file by changing to /usr/share/ssl/certs and > running "make". A script will give you the option to build a PEM > file." > Not on this system, unfortunately. > Firstly, could you show the contents of your log files at the time that a > connect is done. > > Then, try connecting to the service at port 993 with telnet, and see if > the service is actually SSL encoded or not (if you get a plain text > greeting, then it's not). :-) > > Finally, attach to tcpserver or xinetd (or whichever tcp wrapper you are > using) with "strace -s 128 -f -p <pid>", dump the output to a file, then > post a link to the file with passwords removed to this list. > > I'm sure we can figure it out - I have heard of no such problems with > stock Binc IMAP. I'll send that info in a follow up e-mail shortly :) > > Andy :-) > > -- > Andreas Aardal Hanssen > > Thanks for the quick response, Andy! -- "Compassion and retribution are two sides of the same coin. Necessity dictates on what side the coin will fall." "Firearms stand next in importance to the Constitution itself. They are the American people's liberty teeth and keystone under independence." -George Washington
