Rachana--when you say support for this OID has not been added
what do you mean? do you think that this section of the code
threw an exception because the extendedKeyUsage section
of the cert was marked critical when it should not have been,
or would it throw an exception if the extendedKeyUsage
Steve,
The only critical extensions processed by default in the CoG JGlobus
validator are the proxy extensions, basic constraint and key usage.
For other critical extensions policy handler have to be written and
configured. The validator only raises an exception for critical
extensions
Makes sense. Thanks for the explanation Rachana.
-Neha
On Oct 26, 2009, at 9:48 AM, Rachana Ananthakrishnan wrote:
Steve,
The only critical extensions processed by default in the CoG JGlobus
validator are the proxy extensions, basic constraint and key usage.
For other critical extensions
Hi there,
i'm installing Globus 4.2.1 on Debian5 and i'm stuck on the step to prove
that gridftp server works.
I'm following the globus quickstart tutorial on the web.
I've run on separate consoles myproxy client and server, and this is what
each prompts when i try to log in:
In the client
Hi,
I can only guess at what that OpenSSL error message is telling us. Since
the client-side credentials verify OK, maybe there's a problem with the
server's credentials. To check them, run:
grid-proxy-init -debug -verify \
-cert /etc/grid-security/hostcert.pem \
-key
Hi:
First of all, thanks for your answer. Here is the output:
*glo...@debian:/root$ grid-proxy-init -debug -verify-cert
/etc/grid-security/hostcert.pem-key /etc/grid-security/hostkey.pem
User Cert File: /etc/grid-security/hostcert.pem
User Key File: /etc/grid-security/hostkey.pem
That helps us focus the problem investigation. :)
The next reference I suggest is:
http://security.ncsa.uiuc.edu/research/grid-howtos/usefulopenssl.php
I suggest following the Verify A Certificate Matches A Private Key
instructions to confirm that your hostcert.pem and hostkey.pem match.
You
