Dear Markus
You're right! I have to run the globus-update-certificate-dir on the
host with openssl 1.0, and correct it "automaticaly". I could after
choice the good hash one as a defaut CA. Thank's a lot!
Regards
On 12/02/2013 19:35, Markus Binsteiner wrote:
Hi,
not sure whether you are hitting this, but there version of OpenSSL that
globus 5 uses changed and that uses a different name hashing algorithm.
There is a tool called globus-update-certificate-dir that should link
the new hashes to the old files or vice versa, can't remember...
Cheers,
Markus
On Tue, 2013-02-12 at 19:03 -0600, Jerome wrote:
Dear all
I notice a strange error during the definition of my default CA here.
I've using a virtual machine as a SimpleCA, and generate a deb file to
put it on other machines on my grid.
In the first one, when i run the grid-default-ca, i use the hash of my
simpleCA as this:
# grid-default-ca -ca 0cf63ec0
setting the default CA to:
/O=Grid/OU=GlobusTest/OU=simpleCA-simpleca.xxx.xxx.xxx/CN=Globus Simple CA
The file: /etc/grid-security/certificates/grid-security.conf.3a8a9683
does not exist
The CA: /O=Grid/OU=GlobusTest/OU=simpleCA-simpleca.ibt.unam.mx/CN=Globus
Simple CA
has not been setup correctly.
So, why the command is serching a different hash (3a8a9683) that i choice?
--
-- Jérôme
Chaque coup de colère est un coup de vieux,
chaque sourire est un coup de jeune.
(Proverbe chinois)
