Please contact the support channels of whoever set up that server. If
that was you, try to remember how you configured things when you set
them up, and copy that configuration, including the relevant files.

There are a million ways to implement a PKI service, and the details of
where you need to drop those files on the new server depend greatly on
the choices you've made while configuring things.

On 13-06-18 08:29, wrote:
> Yes, that’s right.
> My target is to migrate old server to new one keeping PKI and certificates 
> (included databases).
> After this search how can I manage these files into new server?
> I Should to create multiple directory ? Each one for each index.txt files ? 
> My search found several index.txt files
> It’s necessary to write this directory immediately under openssl directory?
>> On 12 Jun 2018, at 18:30, Jan Just Keijser <> wrote:
>> Hi,
>> On 07/06/18 06:14, Sampei wrote:
>>> t’s a server installed many many years ago and there are applications which 
>>> are no used.
>>> Server is too late and I have new server (latest Centos 6) for migrating 
>>> where I installed latest version.
>>> I’d like to take to new server all certificate database (certificated 
>>> included) which I created.
>>> Openssl is only tool to create test certificates.
>>> I don’t know if there are apps which are using the e configs, but I think 
>>> no.
>> this has little to do with OpenSSL itself and more with PKI management. 
>> Basically, your problem seems to be that you have an older server and you 
>> don't know where the certificates and private keys (i.e. the PKI) were 
>> stored. What you need to do, is find out where the certifcates are held, 
>> together with the index.txt file. In order to do so, you could use something 
>> like
>>   find / -name '*.pem'
>> or
>>   find / -name index.txt
>> and check all directories where such files are found. This will be a lengthy 
>> process, as the find command has to traverse the entire filesystem.
>> good luck,
>> JJK

openssl-users mailing list
To unsubscribe:

Reply via email to