VOMSDIR(5)

πŸ’– vomsdir(5) β€” the VOMS server trust anchor directory, explained by your bestie πŸ’–

okay so. this is the manual page for vomsdir(5), and bestie, it's literally just about a folder. a very important folder. the folder that holds your local info about which VOMS servers you trust. no cap, that's the whole thing. let's get into it 🫢


✨ NAME ✨

vomsdir β€” the structure of the vomsdir VOMS server trust anchor directory πŸ’…


🌸 SYNOPSIS 🌸

/etc/grid-security/vomsdir

πŸ¦‹ DESCRIPTION πŸ¦‹

so this page describes how the vomsdir VOMS server trust anchor directory is structured. what's its job? it keeps local information about trusted VOMS servers, and that info gets used to verify the signatures on the attributes that VOMS servers issue. it's giving trust issues but in a healthy way πŸ’–

the vomsdir directory is structured like this:

<vomsdir>
   |
   |--vo1
   |
   |--vo2
   |
   |--vo3
   |

a subdirectory gets created for each of the trusted VOs. iconic. and inside each VO directory you'll find two types of files:

  • LSC files β€” an LSC file contains a description of the certificate chain of the certificate used by a VOMS server to sign VOMS attributes. πŸ“œ
  • X509 certificates β€” the certificate used by a VOMS server to sign attributes. πŸ”

these files are commonly named using the following pattern:

<hostname>.lsc
<hostname>.pem

where hostname is the host where the VOMS server is running. slay.

⚠️ when both lsc and pem files are present for a given VO and hostname, the lsc file takes precedence. so the lsc is the main character here, periodt.

πŸŽ€ LSC file syntax πŸŽ€

the LSC file contains a list of X.509 subject strings, one on each line, encoded in OpenSSL slash-separated syntax, describing the certificate chain (up and including the CA that issued the certificate). literally one per line, no notes.

for instance, the voms.cnaf.infn.it VOMS server has the following LSC file:

/C=IT/O=INFN/OU=Host/L=CNAF/CN=voms.cnaf.infn.it
/C=IT/O=INFN/CN=INFN CA

see? two lines. the chain. up and including the CA. obsessed 😭✨


🌈 EXAMPLES 🌈

say you locally trust two VOs β€” the cms VO and the cdf VO. then the /etc/grid-security/vomsdir directory will be structured as follows:

/etc/grid-security/vomsdir
/etc/grid-security/vomsdir/cms
/etc/grid-security/vomsdir/cdf

the /etc/grid-security/vomsdir/cms directory will contain the following files:

lcg-voms.cern.ch.lsc
voms.cern.ch.lsc

the /etc/grid-security/vomsdir/cdf directory will contain the following files:

voms-01.pd.infn.it.lsc
voms.cnaf.infn.it.lsc
voms.fnal.gov.lsc

and the LSC files will contain descriptions of the certificate chains used by VOMS servers to sign attribute certificates. that's the vibe check, passed βœ…


πŸ’€ BUGS πŸ’€

to report bugs or ask for support, use GGUS: https://ggus.eu/pages/home.php

like, actually use it. don't just suffer in silence, bestie πŸ™ˆ


πŸ‘‘ AUTHORS πŸ‘‘

  • Enrico Vianello enrico.vianello@cnaf.infn.it
  • Francesco Giacomini francesco.giacomini@cnaf.infn.it

kings. we stan 🫢


⭐ SEE ALSO ⭐

voms-proxy-destroy(1), voms-proxy-info(1), voms-lsc(5)

iykyk πŸ’…


okay that's the whole page, bestie β€” go forth and trust your VOMS servers responsibly πŸŒΈπŸ¦‹πŸ’–

this was the vomsdir(5) page, dated 2026-10-09. mwah, no notes πŸ’‹βœ¨

πŸ“¦ where this page comes from