• anarcat's avatar
    parse gpg.conf for the default-key setting · 2d5df2b4
    anarcat authored
    we would previously copy the gpg.conf to the temporary keyring, which
    works, but then when we actually sign the key, we iterate over the
    secrets to figure out which key to use, and then the default-key
    setting is ignored.
    
    instead, we simply parse the gpg.conf by hand to detect the
    setting. we could have used gpgconf, but this doesn't seem easier to
    parse and adds yet another dependency. i would argue it is easier and
    simpler to parse the config file than to shell out to yet another
    obscure gpg command.
    
    this is a finalization of #721599
    2d5df2b4
Name
Last commit
Last update
.gitlab/issue_templates Loading commit data...
debian Loading commit data...
doc Loading commit data...
monkeysign Loading commit data...
po Loading commit data...
scripts Loading commit data...
.gitignore Loading commit data...
.gitlab-ci.yml Loading commit data...
CHANGELOG Loading commit data...
CONTRIBUTING.rst Loading commit data...
LICENSE Loading commit data...
README.rst Loading commit data...
setup.cfg Loading commit data...
setup.py Loading commit data...