[cobalt-users] Re: [cobalt-users]The Final Chapter:: Moving SSL to Raq3

[David Thurman <dthurman@xxxxxxxxxxxxxxxxxxxx>]

on 10-5-01 1:23 AM, Paul Harvey at paul@xxxxxxxxxxxxx was reported to have
made a statement that said this:

Yeah it's Over!!!!!!

> Yes.  I took a copy of all the files in the certs directory.  Set up the
> website on a different machine.  Pointed the DNS to the new IP address.
> Copied the certs to the new setup. Engaged SSL on the GUI and all works
> fine.  It did not seem to matter that it was on a new IP address.   Cert
> used was from Thwarte
> 
> I have seen some of the posts here and others have had problems.  Can't tell
> you why mine worked and others did not.
> 
> 
> ----- Original Message -----
> From: "David Thurman" <dthurman@xxxxxxxxxxxxxxxxxxxx>
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Sent: Thursday, October 04, 2001 1:59 PM
> Subject: Re: [cobalt-users] Moving SSL to Raq3
> 

>>>>>> Has anyone successfully moved a current certificate from one server
> to a
>>>>>> Raq3 if possible and gotten it to work.
>> 
>>>>> The cert is keyed specifically to the machine it's generated for
>>>>> and won't work anywhere else.  Wish I had better news for you I called

(A) You where correct. After calling Cobalt because I tried every suggestion
was told going from Debian to Raq would not work. Did a revoke and replace
with Verisign. All is well now:) Followed the Raq3 manual to the T and was
shocked that something worked as described:)

>>> When you move a key to a new server, you need BOTH parts, chances are
> tho,
>>> their old isp won't give you that , and the customer doesn't have it
>>> either, because they never had it, at best they got the CSR.

(B) Well of course the ISP they had didn't even give the client all her
files.  They even refused to kill DNS or her site now that I have it changed
with InterNIC and on my DNS servers. Add the fact that they setup the domain
and couldn't find the password to get into the web interface to make
changes. Felt like I was dealing with the Mob. Every step was met with
resistance. To think I am the preferred web development company. Hate to see
what they do to people they don't like.

>>> If you do get it, you still need it to match the server type, and the
>>> server has to support the encryption type used to encode the keys unless
>>> they are stripped (eg no password is encoded in the private key)
>>> 
>>> if you can do all that, you can make it work, but you will have to sneak
>>> by the raq's interface to stick the private key in, normally you create
>>> that on the server, in this case you need to use one that already
>>> exists...
 
See (A).

--
Thank you,
David E Thurman
Web Presence Group
309.676.5688
dthurman@xxxxxxxxxxxxxxxxxxxx
http://www.webpresencegroup.net