puffymist

In which case, I'd like to add my bug report because my symptoms might be the same as yours. **Version info** - OS: Windows 10 Home, Version 22H2, Build 19045.4412...

```bash time git verify-commit --raw COMMIT_ID ``` 1. **Before unlocking keyring** ``` real 0m6.394s user 0m0.000s sys 0m0.015s ``` 2. **After unlocking keyring** by signing a commit in Git Bash...

> (notably I just ran the same command twice, not signing anything inbetween) Then our 2 bugs are different. (For me, I could repeatedly run `time git verify-commit --raw COMMIT_ID`...

(My bug is likely different from @Toby222's) I've found another way to make signature verification not timeout: `gpg --verify SIGNED_MESSAGE`: 1. From a cold start of Windows, `git verify-commit` takes...

> I also see you using the `time` command, so I'd think you're on Linux I'm on Windows 10. Git Bash in [Git for Windows](https://gitforwindows.org) provides some Unix utilities, including...

Thanks for fixing the signature verification timeout! For the passphrase not caching problem, should I open a new issue? But note that I'm `Using Git: C:\Program Files\Git\cmd\git.exe (system)`, which is...

Good for you! Sadly, uninstalling GPG4Win didn't fix it for me on Windows 10.