Roman Zeyde
Roman Zeyde
I have squashed all the changes above into a single commit: f16310f03eb71bf4c40b124e2c04df15251bbd41. Please review it - it should contain the same code as https://github.com/romanz/trezor-agent/pull/358/commits/e11afff47d48dc45b13dce3f727be26417364757 above: ``` $ git diff e11afff...
It seems that CI didn't run on this PR... My bad - fixed in 2b49eacc01b45caa5c7da379b54378d58e60bdd7 (please rebase over latest `master`).
> @romanz Anything else needed to get this merged? Will do the final review this weekend - many thanks for the contribution!
I also tested it using `fake-device` agent (on 3c45889), and it seems that regular GPG identity fails to sign: ``` $ gpg --version gpg (GnuPG) 2.2.27 $ export GNUPGHOME=/tmp/gnupg $...
Resolved in latest release.
Which TREZOR device are you using (model One / T)? Also, could you please run `trezor-agent` with higher verbosity logging (using `-vvv`) and attach the full log?
Could you please test #358 to see if it helps with this use-case?
Closing, since it's already supported (#411).
First of all - I am very sorry for the very delayed response! My original idea was to version and release `libagent` and `trezor-agent` separately, but I think that you're...
If a passphrase usage is enabled, it will be used to derive the GPG secret key.