[pubcookie-users] pubcookie new key

Nathan Dors dors at cac.washington.edu
Wed Jun 20 08:15:15 PDT 2007


This looks like a typo in your config file, unless your keyserver 
is really running on port 80. Port 2222 is more common.

As for the ssl_ca_file, it should point to a source of trusted CA 
root certificates. ca-bundle.crt is used as an example, based on 
the bundle of root certs that comes with openssl.

-Nathan

On Sat, 16 Jun 2007, Victor Sterpu wrote:

> When I run keyclient command I receive the following message:
> Failed: HTTP/1.1 200 OK
> Date: Sat, 16 Jun 2007 15:51:15 GMT
> Server: Apache/2.2.3 (CentOS)
> Last-Modified: Fri, 15 Jun 2007 13:30:17 GMT
> ETag: "91010a-4-d90f2c40"
> Accept-Ranges: bytes
> Content-Length: 4
> Connection: close
> Content-Type: text/html; charset=UTF-8
>
> test
>
> I don't know what this message means, but no new key appears in the 
> /usr/local/pubcookie/keys directory.
> Is this an error message?
> If it is how can I fix this?
>
> This is my config file:
> logging_level: 5
> ssl_key_file: /usr/local/pubcookie/ambratest.ambra.ro.crt/server.key
> ssl_cert_file: /usr/local/pubcookie/ambratest.ambra.ro.crt/server.crt
> keymgt_uri: https://www.ambratest.ambra.ro
> ssl_ca_file: /usr/local/pubcookie/ambratest.ambra.ro.crt/server.crt
>
> The ssl_ca_file is the same with ssl_cert_file is the same with the 
> ssl_ca_file becouse I don't know how to generate ca-bundle.crt.
>
> Thank you.
>
> _______________________________________________
> pubcookie-users mailing list
> pubcookie-users at u.washington.edu
> http://mailman1.u.washington.edu/mailman/listinfo/pubcookie-users
>


More information about the pubcookie-users mailing list