summaryrefslogtreecommitdiff
path: root/var
diff options
context:
space:
mode:
authorpsakievich <psakiev@sandia.gov>2024-04-01 12:11:13 -0600
committerGitHub <noreply@github.com>2024-04-01 11:11:13 -0700
commit7afa949da1ee560760aaa700724f9a0466429218 (patch)
tree1a6ff3b5d35acac4ea26d4523371311c1b6df9d4 /var
parentb81d7d0aac713039794cb33860637fb010983dd9 (diff)
downloadspack-7afa949da1ee560760aaa700724f9a0466429218.tar.gz
spack-7afa949da1ee560760aaa700724f9a0466429218.tar.bz2
spack-7afa949da1ee560760aaa700724f9a0466429218.tar.xz
spack-7afa949da1ee560760aaa700724f9a0466429218.zip
Add handling of custom ssl certs in urllib ops (#42953)
This PR allows the user to specify a path to a custom cert file (or directory) in Spack's config: ```yaml # This is where custom certs for proxy/firewall are stored. # It can be a path or environment variable. To match ssl env configuration # the default is the environment variable SSL_CERT_FILE ssl_certs: $SSL_CERT_FILE ``` `config:ssl_certs` can be a path to a file or a directory, or it can be and environment variable that resolves to one of those. When it posts to something valid, Spack will update the ssl context to include custom certs, and fetching via `urllib` and `curl` will trust the provided certs. This should resolve many issues with fetching behind corporate firewalls. --------- Co-authored-by: psakievich <psakievich@users.noreply.github.com> Co-authored-by: Alec Scott <alec@bcs.sh>
Diffstat (limited to 'var')
0 files changed, 0 insertions, 0 deletions