HTPROXYPUT(1)

💖 HTPROXYPUT 💖

okay bestie, listen up — this is the manual page for htproxyput from the GridSite Manual, and it's genuinely such a slay little tool. It's giving "I delegate your GSI proxy so you don't have to." Let's get into it. 🫶

---

✨ NAME ✨

htproxyput, htproxydestroy, htproxytime, htproxyunixtime, htproxyrenew — GSI proxy delegations and querying, using the GridSite/gLite delegation API. 💅

(and yes, htproxyinfo is in the mix too, we'll get to her)

---

🌈 SYNOPSIS 🌈

htproxyput, htproxydestroy, htproxytime, htproxyunixtime, htproxyrenew
[options] Service-URL

htproxyinfo [options]

literally that's it. one URL, some options, and vibes. ✨

---

🦋 DESCRIPTION 🦋

So htproxyput is a client that performs GSI proxy delegations using the GridSite/gLite delegation Web Service portType. Think of her as the bestie who goes and puts your proxy where it needs to be. And gridsite-delegation(8)? That's the complementary server-side implementation — the other half of the duo, the main character to her co-star. 👑

Then there's htproxyinfo, who does something slightly different: she examines a local copy of a GSI proxy and outputs a summary of its X.509 and VOMS contents. nosy? maybe. useful? absolutely. 🔍

---

💅 OPTIONS 💅

• -v/--verbose — turn on debugging information. she's chatty and we love that for her. 🗣️
• --delegation-id <ID> — explicitly specify the Delegation ID to use. no guessing, you tell her exactly which ID. 🎀
• --destroy — instead of delegating a proxy, delete the proxy from the service's proxy cache. Calling the program as htproxydestroy has the same effect. bye bestie 💀
• --time — instead of delegating a proxy, report the expiration time of the proxy, in the local time of the client. Calling the program as htproxytime has the same effect. ⏰
• --unixtime — instead of delegating a proxy, report the expiration time of the proxy, as the number of seconds since 00:00:00 1970-01-01 UTC. Calling the program as htproxyunixtime has the same effect. raw timestamp energy, no cap. 🔢
• --renew — delegate an updated version of an existing proxy. The Delegation ID must be given when using this option. Calling the program as htproxyrenew has the same effect. glow-up arc ✨
• --info — examine a local proxy file, and output a summary of the X.509 certificates and VOMS attributes it contains. Calling the program as htproxyinfo has the same effect. 🕵️♀️
• --cert <X.509 cert path> and --key <X.509 key path> — path to the PEM-encoded X.509 or GSI Proxy user certificate and key to use for HTTPS connections, instead of "anonymous mode." If only one of --key or --cert is given, then that will be tried for both. If neither is given, then the following order of precedence is used: the file name held by the variable X509_USER_PROXY; the file /tmp/x509up_uID (with Unix UID equal to ID); the file names held by X509_USER_CERT / X509_USER_KEY; the files ~/.globus/usercert.pem and ~/.globus/userkey.pem (where ~/ is the home directory of the user.) 🔑
• --capath <X.509 CA root certs directory or file> — path to the PEM-encoded CA root certificates to use when verifying remote servers' host certificates in HTTPS connections. Ideally this should be a directory of hash.0 files as described in the OpenSSL verify(1) man page, but a file may be used instead. If --capath is not given, the value of the environment variable X509_CERT_DIR will be tried. If this is not valid, then /etc/grid-security/certificates will be used. 🌳
• --no-verify — do not use CA root certificates to verify remote servers' host certificates. This is useful for testing sites before their certificate is set up properly, but leaves you vulnerable to "man in the middle" attacks by hostile servers masquerading as your target. ⚠️

okay so --no-verify is genuinely giving chaos. fine for a lil test, not fine for real life. hostile servers cosplaying as your target is NOT the vibe. 🙈

---

🍓 FILES 🍓

• /tmp/x509up_uID — default GSI Proxy file for Unix UID equal to ID. 🏠
• /etc/grid-security/certificates — default location for trusted Certification Authority root certificates to use when checking server certificates. 📁
• /tmp/.ca-roots-XXXXXX — prior to 7.9.8, the underlying curl library did not support the CA root certificates directory. If built with an old version of libcurl, htproxyput will concatenate the certificates in the CA roots directory into a unique temporary file and use that. throwback lore 🕰️

---

🌸 ENVIRONMENT 🌸

• X509_CERT_DIR — holds directory to search for Certification Authority root certificates when verifying server certificates. (Tried if --capath is not given on the command line.) 🌲
• X509_USER_PROXY — holds file name of a GSI Proxy to use as user certificate. (Tried if --cert or --key are not given on the command line.) 🪪
• X509_USER_CERT and X509_USER_KEY — holds file name of X.509 user certificate and key. (Tried if X509_USER_PROXY is not valid.) 🗝️

---

⭐ EXIT CODES ⭐

0 is returned on complete success, and non-zero on error. periodt. 💯

---

🧚 TO DO 🧚

Better error recovery. (she's working on herself, okay?? growth era 🌱)

---

👑 AUTHOR 👑

Andrew McNab <Andrew.McNab@manchester.ac.uk>

htproxyput is part of GridSite: http://www.gridsite.org/ 🌐

---

💜 SEE ALSO 💜

htcp(1), gridsites-delegation(8)

wait no — gridsite-delegation(8) bestie, my bad 😭 go read those too, iykyk.

---

and that's the whole page!! 🎀 this beauty is htproxyput, and she came to us in March 2006 — iconic since day one, fr fr. go delegate something. 💖✨🦋