Stevie Beth Mhaol
Stevie Beth Mhaol
A better form of the workaround is: ``` gpg --no-default-keyring --keyring .blackbox/pubring.kbx --export -a | gpg --import ``` `--no-default-keyring` prevents gpg from also exporting the default keyring, which is pointless...
Printing binary data as utf8 seems like a bad approach, because utf8 has sequences of bytes which are invalid.
Hmm, k. Looking at kr, i don't see any way to support making multi-line output readable for humans. Assuming that is the case, do you think it would be possible...
It wouldn't be hard to make it machine readable (e.g. by prefixing all of the lines with something like `>`), just not within logfmt.
I've updated the PR and gist with a machine-readable representation.
Rebased and updated. We've been using this for the last 2 years, and have tooling which parses the output.
We've been using this for the last 3 years and it's worked fine. Rebased on master, just in case there's a chance of getting it merged :)
I've been working on a dokuwiki integration. The very rough first version is here: https://github.com/kormat/aauth-dokuwiki. A corp-mate has been working on the dokuwiki plugin: https://github.com/pcd1193182/dokuwiki-discourse-sso. N.B.: **It Does Not Work...
@JelleZijlstra: if it's not a bug, then i'm not sure how the `python_version` feature is useful. The default mypy settings [ignore errors in site-packages](https://mypy.readthedocs.io/en/stable/config_file.html#confval-no_silence_site_packages). The fact that `python_version` doesn't follow...