search

jorgelbg / pinentry-touchid

Custom GPG pinentry program for macOS that allows using Touch ID for fetching the password from the macOS keychain.
Apache License 2.0
521 stars 23 forks source link

gpg: signing failed: Bad Passphrase #31

Open Truckerbug opened 1 year ago

Truckerbug commented 1 year ago

Happens when I run $ echo "1234" | gpg -as - Reset Passphrase used from TouchID?

(using) M1 Mac GPG $ gpg --version

gpg (GnuPG) 2.3.7 libgcrypt 1.10.1 Copyright (C) 2021 Free Software Foundation, Inc. License GNU GPL-3.0-or-later https://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.

Home: /Users/truckerbug/.gnupg Supported algorithms: Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 AEAD: EAX, OCB Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2

Configuration

gpg:OpenPGP:/opt/homebrew/Cellar/gnupg/2.3.7_1/bin/gpg gpgsm:S/MIME:/opt/homebrew/Cellar/gnupg/2.3.7_1/bin/gpgsm keyboxd:Public Keys:/opt/homebrew/Cellar/gnupg/2.3.7_1/libexec/keyboxd gpg-agent:Private Keys:/opt/homebrew/Cellar/gnupg/2.3.7_1/bin/gpg-agent scdaemon:Smartcards:/opt/homebrew/Cellar/gnupg/2.3.7_1/libexec/scdaemon dirmngr:Network:/opt/homebrew/Cellar/gnupg/2.3.7_1/bin/dirmngr pinentry:Passphrase Entry:/opt/homebrew/opt/pinentry/bin/pinentry

Logs

gpg-agent:

/.gnupg/gpg-agent.log:

gpg-agent.log

pinentry-touchid also generates its own log which you can find in $TMPDIR/pinentry-touchid.log: 2022/09/06 11:29:15 main.go:118: Ready! 2022/09/06 11:31:17 main.go:118: Ready! 2022/09/06 11:38:37 main.go:118: Ready! 2022/09/06 11:39:20 main.go:118: Ready! 2022/09/06 11:40:08 main.go:118: Ready! 2022/09/06 20:41:06 main.go:118: Ready! 2022/09/06 20:41:43 main.go:118: Ready! 2022/09/06 20:45:47 main.go:118: Ready! 2022/09/06 20:50:07 main.go:118: Ready! 2022/09/06 20:50:11 main.go:118: Ready! 2022/09/06 20:50:13 main.go:348: Failed to authenticate 2022/09/06 20:50:30 main.go:118: Ready! 2022/09/06 20:50:32 main.go:348: Failed to authenticate 2022/09/06 20:50:34 main.go:118: Ready! 2022/09/06 20:51:58 main.go:118: Ready! 2022/09/06 20:54:09 main.go:118: Ready! 2022/09/06 20:54:30 main.go:118: Ready! 2022/09/06 20:54:34 main.go:348: Failed to authenticate 2022/09/06 20:54:35 main.go:118: Ready! 2022/09/06 20:54:37 main.go:348: Failed to authenticate 2022/09/06 20:55:47 main.go:118: Ready! 2022/09/06 20:58:17 main.go:118: Ready! 2022/09/06 20:58:19 main.go:348: Failed to authenticate 2022/09/06 20:58:21 main.go:118: Ready! 2022/09/06 20:58:22 main.go:348: Failed to authenticate 2022/09/06 20:58:36 main.go:118: Ready! 2022/09/06 21:00:16 main.go:118: Ready! 2022/09/06 21:00:21 main.go:118: Ready! 2022/09/06 21:00:29 main.go:118: Ready! 2022/09/06 21:01:37 main.go:118: Ready! 2022/09/06 21:01:40 main.go:348: Failed to authenticate 2022/09/06 21:01:41 main.go:118: Ready! 2022/09/06 21:01:42 main.go:348: Failed to authenticate 2022/09/06 21:01:47 main.go:118: Ready! 2022/09/06 21:01:50 main.go:348: Failed to authenticate 2022/09/06 21:04:48 main.go:118: Ready! that's all I can say for right now