[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Thawte CSR
- Subject: Re: [cobalt-users] Thawte CSR
- From: "Brian Emerson" <bemerson71@xxxxxxxxxxxx>
- Date: Fri Apr 20 11:35:05 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> > Hello All,
> >
> > I currently have a RAQ3 with a Thawte SSL cert installed. It is up for
> > renewal, but since Thawte changed their database, they now require the
> > 'State' to be spelled out instead of 2 character abbreviation. In order
to
> > make this change, I need to regenerate a new CSR from my RAQ. How do I
do
> > this without disrupting my production cert? Any insight would be greatly
> > appreciated.
> >
> > Regards,
> > Brian Emerson
>
>
> Dear Brian,
>
> Since there dosent appear to be an answer on the Users group I
> have posted this to the developers group... I asked t his same
> question last week and there were no helpful replies.
>
> Cheers, Lennie Core
>
> ---------------------------------------------------
> Lennie Core, Ceo
> Coreave.com, Design & Hosting
> 757-442-6240
> http://coreave.com
>
Hello Lennie,
Thanks for the follow up, but I have got it figured out. Here are the steps
I took...
1. I took a second development server and named it the same as my production
server.
2. I then generated a self-signed cert on the dev server, using the same
information as the production server, except I spelled out the State in
full.
3. I gave the CSR from the development server to Thawte. Within an hour,
they gave me the updated certificate.
4. I opened a SSH session to the production server, cd to
/home/sites/home/certs . Deleted the files named 'certificate', 'key', 'and
'request' (backed them up first, of course!).
5. Created 3 new files
1. - certificate - Put the new certificate from Thawte in this file.
2. - request - Put the contents from the 'request' file off the dev
server into this one.
3. - key - Put the contents of the 'key' file off the dev server
into this one.
6. Rebooted the production server, and it took off running!
Regards,
Brian Emerson