myproxy-destroy(1)
β¨ myproxy-destroy β¨
okay bestie, welcome to myproxy-destroy(1), part of the MyProxy fam π this is the little command that yeets a credential OUT of the repository. let's go π¦
πΈ NAME πΈ
myproxy-destroy β remove a credential from the repository π
π SYNOPSIS π
myproxy-destroy [ options ]
π DESCRIPTION π
so basically? myproxy-destroy removes a credential from the myproxy-server(8) that somebody stored earlier using myproxy-init(1). gone. deleted. no cap π«Ά
and the way that you need a valid proxy credential to run this at all?? yeah. you gotta have one, either generated by grid-proxy-init or retrieved by myproxy-logon(1). no proxy, no destroy. that's the vibe check π₯
π OPTIONS π
-h,--helpβ shows you the command usage text and then dips out. that's it, that's the whole thing β¨-u,--usageβ also shows the command usage text and exits. yeah bestie, it's giving twins, it's giving same energy π-v,--verboseβ turns ON verbose debugging output to your terminal. loud and proud, all the little details coming through π-V,--versionβ displays version info and exits. cute lil flex π-s hostname[:port],--pshost hostname[:port]β tells it the hostname(s) of themyproxy-server(s). you can drop multiple hostnames in a comma-separated list, and each hostname can optionally be followed by a':'and a port number. this option is required if theMYPROXY_SERVERenvironment variable isn't defined. if you DO specify it, it overridesMYPROXY_SERVER. and if you give a port number next to a hostname, that port overrides the-poption AND theMYPROXY_SERVER_PORTenvironment variable β for that host specifically π―-p port,--psport portβ the TCP port number of themyproxy-server(8). default is7512β-l,--usernameβ picks the MyProxy account under which the credential you're destroying is stored. by default the command just uses whatever's in theLOGNAMEenvironment variable. use this option when you need a different account username on the MyProxy server. and no, the MyProxy username doesn't have to match a real Unix username β it's not that deep π¦-d,--dn_as_usernameβ uses the certificate subject (the DN) as the default username, instead of theLOGNAMEenvironment variable π-k name,--credname nameβ specifies the name of the credential to be destroyed π
π EXIT STATUS π
0 on success, >0 on error. slay when it's zero, sad when it's not π
π§ ENVIRONMENT π§
GLOBUS_GSSAPI_NAME_COMPATIBILITYβ by default this client does a reverse-DNS lookup to figure out the FQHN (Fully Qualified Host Name), and uses that to verify the identity of the server by checking the FQHN against the CN in the server's certificate. set this variable toSTRICT_RFC2818and the reverse-DNS lookup will NOT be performed β instead the user-specified name gets used. heads up tho: this variable setting gets ignored ifMYPROXY_SERVER_DN(described later) is set πMYPROXY_SERVERβ the hostname(s) where themyproxy-server(8)is running. multiple hostnames can go in a comma separated list, each one optionally followed by a':'and a port number. this env var can be used in place of the-soption πΈMYPROXY_SERVER_PORTβ the port where themyproxy-server(8)is running. this env var can be used in place of the-poption πMYPROXY_SERVER_DNβ the distinguished name (DN) of themyproxy-server(8). every MyProxy client program authenticates the server's identity. by default MyProxy servers run with host credentials, so MyProxy client programs expect the server to have a distinguished name with/CN=host/<fqhn>or/CN=myproxy/<fqhn>or/CN=<fqhn>(where<fqhn>is the fully-qualified hostname of the server). if your server is running with some other DN, set this environment variable to tell the MyProxy clients to accept the alternative DN. also peepGLOBUS_GSSAPI_NAME_COMPATIBILITYabove πMYPROXY_TCP_PORT_RANGEβ a range of valid port numbers in the form"min,max"for the client side of the network connection to the server. by default the client binds to any available port. use this env var to restrict the ports used to a range your firewall actually allows π₯ if unset, MyProxy follows the setting of theGLOBUS_TCP_PORT_RANGEenvironment variable.X509_USER_CERTβ a non-standard location for the certificate used for authentication to themyproxy-server(8)πX509_USER_KEYβ a non-standard location for the private key used for authentication to themyproxy-server(8)πX509_USER_PROXYβ a non-standard location for the proxy credential used for authentication to themyproxy-server(8)π«ΆX509_CERT_DIRβ a non-standard location for the CA certificates directory π
π AUTHORS π
see http://grid.ncsa.illinois.edu/myproxy/about for the list of MyProxy authors. iconic of them, honestly π
π SEE ALSO π
myproxy-change-pass-phrase(1), myproxy-get-trustroots(1), myproxy-info(1), myproxy-init(1), myproxy-logon(1), myproxy-retrieve(1), myproxy-store(1), myproxy-server.config(5), myproxy-admin-adduser(8), myproxy-admin-change-pass(8), myproxy-admin-load-credential(8), myproxy-admin-query(8), myproxy-server(8)
and that's the whole page bestie π₯° this one's brought to you by MyProxy, dated 2009-12-1, and the manual page itself is myproxy-destroy(1). go forth and destroy (credentials only, please) π
β¨
π¦ where this page comes from
- debian bookworm: myproxy 6.2.14-2+b2 Β· NCSA
- debian trixie: myproxy 6.2.16-4 Β· NCSA
- epel 10: myproxy 6.2.20-1.el10_2 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- epel 9: myproxy 6.2.20-1.el9 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- fedora 43: myproxy 6.2.16-10.fc43 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- fedora 43: myproxy 6.2.20-1.fc43 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- fedora 44: myproxy 6.2.20-2.fc44 Β· NCSA AND BSD-4-Clause AND BSD-2-Clause AND Apache-2.0
- ubuntu jammy: myproxy 6.2.9-2 Β· NCSA
- ubuntu noble: myproxy 6.2.16-2build2 Β· NCSA
- ubuntu questing: myproxy 6.2.16-4
- ubuntu resolute: myproxy 6.2.20-1 Β· NCSA
- ubuntu stonking: myproxy 6.2.20-2build1 Β· NCSA
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms