e10c4fad6e
Some organizations use a firewall that intercepts SSL communications and replaces the authentication token with an organization-wide token that is just supposed to be accepted. Browsers can be locally configured for this intentional trickery, but it's a little more tricky for the use of `curl` in a batch script that is shared with external collaborators. The easiest solution is to just disable the security for the `curl` download. This makes the script more susceptible to "man in the middle" attacks, but it's probably easier to just slip malware in the public repos anyway.
17 lines
478 B
Bash
Executable File
17 lines
478 B
Bash
Executable File
#!/bin/sh
|
|
|
|
set -e
|
|
|
|
readonly version="nvcc_v4"
|
|
readonly sha256sum="260779b4a740fe8373d251d1e318541a98dd5cd2f8051eedd55227a5a852fdf7"
|
|
readonly filename="sccache-0.2.14-$version-x86_64-unknown-linux-musl"
|
|
readonly tarball="$filename.tar.gz"
|
|
|
|
cd .gitlab
|
|
|
|
echo "$sha256sum $tarball" > sccache.sha256sum
|
|
curl --insecure -OL "https://github.com/robertmaynard/sccache/releases/download/$version/$tarball"
|
|
sha256sum --check sccache.sha256sum
|
|
tar xf "$tarball"
|
|
#mv "$filename/sccache" .
|