GRID-CERT-DIAGNOST(1)

💖 grid-cert-diagnostics 💖

okay bestie, welcome to grid-cert-diagnostics(1) — straight outta the Grid Community Toolkit Manual, section 1, and she is THAT girl. she prints out diagnostic info about certificates and keys. let's get into it 🦋

✨ NAME ✨

grid-cert-diagnostics — print diagnostic information about certificates and keys. that's it. that's the whole job. 💅

🌸 SYNOPSIS 🌸

grid-cert-diagnostics [ -h | -help ]

grid-cert-diagnostics [ -p ] [ -n ] [ -c CERTIFICATE [-H HOSTNAME] [-m {
STRICT_GT2 | HYBRID | STRICT_RFC2818 }]]

grid-cert-diagnostics [ -s HOST[:PORT] | -g HOST[:PORT] ] [-m {
STRICT_GT2 | HYBRID | STRICT_RFC2818 }]

🎀 DESCRIPTION 🎀

so like, grid-cert-diagnostics spills ALL the tea about the current user's security environment. we're talking:

• info about security-related environment variables
• the security directory search path
• your personal key and certificates
• and your trusted certificates

the whole point? it's here to hand you information that helps you diagnose problems using GSIC. it's giving helpful, not nosy. 🫶

by default, grid-cert-diagnostics prints out the info about the environment and the trusted certificate directory. but if you pass the -p command-line option, then additional info about the current user's default certificate and key gets printed too. extra credit energy. ✨

and plot twist — grid-cert-diagnostics can also attempt to diagnose problems connecting to remote GridFTP or SSL-based services. she does it all, fr fr. 👑

💅 OPTIONS 💅

the full set of command-line options to grid-cert-diagnostics is literally this whole menu, bestie:

• -h, -help — display a help message and exit. bye, love you, here's the manual. 🎀
• -p — display info about the personal certificate and key that is the current user's default credential.
• -n — check time synchronization with the ntpdate command. clock check, no cap. ⏰
• -c CERTIFICATE, -c - — check the validity of the certificate in the file named by CERTIFICATE, or from standard input if the parameter to -c is -.
• -H HOSTNAME — when you're using the -c option above, check that the certificate's identity matches HOSTNAME.
• -m STRICT_GT2 | HYBRID | STRICT_RFC2818 — use the specified mode when comparing host certificate names.
• -s HOST[:PORT] — connect to the service listening on HOST:PORT and initiate the TLS protocol. diagnostics get printed containing the TLS / SSL protocol version and the available cipher list. the certificate chain will be verified, and the certificate subject name, issuer name, and subjectAltName extensions will be printed. if the :PORT is omitted, the default of 443 is used. 🔥
• -g HOST[:PORT] — similar to the -s option, but use the GridFTP protocol instead. the initial GridFTP banner response is included in the diagnostic output. if the :PORT is omitted, the default of 2811 is used.

🌈 EXAMPLES 🌈

🌸 example one: the default vibe check 🌸

in this example, we see the default mode of checking the default security environment for the system, without processing the user's key and certificate. note the user receives a warning about a cog.properties and about an expired CA certificate. 😭

% grid-cert-diagnostics

Checking Environment Variables
==============================
Checking if X509_CERT_DIR is set... no
Checking if X509_USER_CERT is set... no
Checking if X509_USER_KEY is set... no
Checking if X509_USER_PROXY is set... no

Checking Security Directories
=======================
Determining trusted cert path... /etc/grid-security/certificates
Checking for cog.properties... found
    WARNING: If the cog.properties file contains security properties,
             Java apps will ignore the security paths described in the GSI
             documentation

Checking trusted certificates...
================================
Getting trusted certificate list...
Checking CA file /etc/grid-security/certificates/1c4f4c48.0... ok
Verifying certificate chain for "/etc/grid-security/certificates/1c3f2ca8.0"... ok
Checking CA file /etc/grid-security/certificates/9d8788eb.0... ok
Verifying certificate chain for "/etc/grid-security/certificates/9d8753eb.0"... failed
    globus_credential: Error verifying credential: Failed to verify credential
    globus_gsi_callback_module: Could not verify credential
    globus_gsi_callback_module: The certificate has expired:
    Credential with subject: /DC=org/DC=example/OU=grid/CN=CA has expired.

🦋 example two: the mismatched key moment 🦋

in this example, we show a user with a mismatched private key and certificate. not the cert and the key being in their enemies-to-lovers era, just… not matching. 🙈

% grid-cert-diagnostics -p

Checking Environment Variables
==============================
Checking if X509_CERT_DIR is set... no
Checking if X509_USER_CERT is set... no
Checking if X509_USER_KEY is set... no
Checking if X509_USER_PROXY is set... no

Checking Security Directories
=======================
Determining trusted cert path... /etc/grid-security/certificates
Checking for cog.properties... not found

Checking Default Credentials
==============================
Determining certificate and key file names... ok
Certificate Path: "/home/juser/.globus/usercert.pem"
Key Path: "/home/juser/.globus/userkey.pem"
Reading certificate... ok
Reading private key...
ok
Checking Certificate Subject...
"/O=Grid/OU=Example/OU=User/CN=Joe User"
Checking cert... ok
Checking key... ok
Checking that certificate contains an RSA key... ok
Checking that private key is an RSA key... ok
Checking that public and private keys have the same modulus... failed
Private key modulus: D294849E37F048C3B5ACEEF2CCDF97D88B679C361E29D5CB5
219C3E948F3E530CFC609489759E1D751F0ACFF0515A614276A0F4C11A57D92D7165B8
FA64E3140155DE448D45C182F4657DA13EDA288423F5B9D169DFF3822EFD81EB2E6403
CE3CB4CCF96B65284D92592BB1673A18354DA241B9AFD7F494E54F63A93E15DCAE2
Public key modulus : C002C7B329B13BFA87BAF214EACE3DC3D490165ACEB791790
600708C544175D9193C9BAC5AED03B7CB49BB6AE6D29B7E635FAC751E9A6D1CEA98022
6F1B63002902D6623A319E4682E7BFB0968DCE962CF218AAD95FAAD6A0BA5C42AA9AAF
7FDD32B37C6E2B2FF0E311310AA55FFB9EAFDF5B995C7D9EEAD8D5D81F3531E0AE5
Certificate and and private key don't match

yes bestie, that last line really does say "and and". we are keeping it exactly as written. no notes. 💀

👑 AUTHOR 👑

Copyright © 1999-2015 University of Chicago. iconic of them honestly. 🫶

and that's the whole page, bestie!! 💖 this was Grid Community Toolkit 6, dated 03/31/2018 — mwah, go check your certs, ily, bye!! ✨🎀🦋