diff options
| author | Harmen Stoppels <harmenstoppels@gmail.com> | 2021-08-26 21:59:44 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-08-26 12:59:44 -0700 |
| commit | 23106ac0f55623a155c1e74633890f7fb7d52d36 (patch) | |
| tree | 66b39efc8c7b251549a927ef33bb7d0dddce3b8f /bin/spack-python | |
| parent | 29d1bc6546def4bcd09c0a5b533de9f39a78d910 (diff) | |
| download | spack-23106ac0f55623a155c1e74633890f7fb7d52d36.tar.gz spack-23106ac0f55623a155c1e74633890f7fb7d52d36.tar.bz2 spack-23106ac0f55623a155c1e74633890f7fb7d52d36.tar.xz spack-23106ac0f55623a155c1e74633890f7fb7d52d36.zip | |
Set pubkey trust to ultimate during `gpg trust` (#24976)
* Set pubkey trust to ultimate during `gpg trust`
Tries to solve the same problem as #24760 without surpressing stderr
from gpg commands.
This PR makes every imported key trusted in the gpg database.
Note: I've outlined
[here](https://github.com/spack/spack/pull/24760#issuecomment-883183175)
that gpg's trust model makes sense, since how can we trust a random
public key we download from a binary cache?
* Fix test
Diffstat (limited to 'bin/spack-python')
0 files changed, 0 insertions, 0 deletions