Hello, On Thu, Jun 22, 2006 at 07:29:08PM +0300, Black Dew wrote: | Zane Dodson wrote: | >On Thu, Jun 22, 2006 at 09:27:56AM -0400, S Scharf wrote: | >| I am running a server on Debian Stable (sarge). I configured the | >| machine under one domain name (example.info) and then renamed | >| it (example.com) when deploying it as my main server. The SSL | >| certificates all contain the origional (example.info) domain. How do | >| I generate new certificates with the new correct name? | > | >You can generate another key for the host with ssh-keygen(1). You may | >also find it helpful to consult | > /usr/share/doc/openssh-server/README.Debian.gz | | He's talking about SS_L_ an not SS_H_
Oops, I read the OP's message too hastily. I should have noted the subject more carefully and the use of *certificate* rather than *key* above. | SSH keys are not bound to domain name anyway afaik. Yes, I think this is true too. But IMO it is not a good idea to try to move them to another system. | Now for SSL - that depends for which package do you need to update them. True. There are likely many different certificates in use. openssl(1) can be used to generate another one (self-signed). If it was generated automatically for you, you can probably find how it was generated in the postinst script for the relevant package in /var/lib/dpkg/info. Thanks for pointing out my error and my apologies to the OP. Best regards, -- Zane Dodson ZDodson Consulting, Inc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
