So it turns out that it was indeed a stupid mistake :(
I forgot to supply the :ssl-privatekey-file keyword argument.
SBCL (using CL+SSL) gives much more descriptive error message and that's how I track down the problem.
Sorry for the false alarm !
Regards, -- Mac
On 7/8/07, Mac Chan emailmac@gmail.com wrote:
Hi,
Have anyone successfully started a https server with the latest hunchentoot?
For some reason I'm getting a "no shared cipher" error. I hoped that I'm not making stupid mistake with the ssl setup.
# To generate a key $ openssl genrsa 1024 > server.key
# To generate a Certificate Signing Request $openssl req -new -key server.key > server.csr
# self-sign cert $openssl req -x509 -key server.key -in server.csr > server.crt
(asdf:oos 'asdf:load-op :hunchentoot-test)
(hunchentoot:start-server :port 4443 :ssl-certificate-file "server.crt")
(setq hunchentoot:*catch-errors-p* nil)
When I point firefox to https://localhost:4443/, a error dialog pops up:
`Firefox and localhost cannot communicate securely because they have no common encryption algorithms.'