Perhaps this has been covered on this list before, but I haven't unearthed where. So, bear with me.
Scenario: I'm trying to configure courier-imapd-ssl on a gentoo Linux server. I have courier imapd installed, and the plain server works very well. Also, the mkimapdcert app makes a "demo" cert that works. Now, I know this is really an Openssl question, but noone on openssl-users was willing to help me out; so I turned here. What are the actual arguments that mkimapdcert sends to openssl to get the functional signed cert for imapd-ssl? I looked over the imapd.cnf file, but that doesn't hold the openssl command arguments. Connecting to the server using mutt gets an I/O for every cert that I generate - even the one (seemingly) with no passphrase on the key. So, what are the specific commands that need to be fed to openssl to get a self-signed cert that will work with imapd-ssl? I do have a functional Openssl demoCa setup working. Thanks. geoffrey -- ++++++++++++++++++++++++++ This space intentionally left non-blank ++++++++++++++++++++++++++ _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
