Certificate simple question

[Thomas Spuhler]

On Wednesday 16 May 2007 07:12, ITSEF Admin wrote:
> On Wednesday 16 May 2007 13:06, Divan Santana wrote:
> > When I installed Kolab 2.1 I installed using a wrong FQDN.
> >
> > Now I simply want to change my certificate.
> >
> > So how I plan on doing this is simply install kolab 2.1 on a test box
> > with the correct certificate details when I run
> > "/kolab/etc/kolab/kolab_bootstrap -b" and then copy the cert.pem and
> > key.pem to /kolab/etc/kolab on the live box and restart kolab.
> >
> > Is that safe and correct?
>
> Yes, that's possible, but you don't need to build another kolab
> installation for this. You can either generate the certificate yourself
> with openssl (rather cumbersome) or you can use a program to administrate
> the certificate. I'm using TinyCA here to do just that. The nice thing
> about this is that you can also adminster client certificates with TinyCA
> and it will also generate the necessary CRL (certificate revocation list)
> for you. Very nice. :-)
>
> Cheerio,
>
> Thomas
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users at kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

There is a script in kolab that will create it. Why not use that?


Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20070516/cb49fe3d/attachment.sig>