Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> writes: > Orthogonal to that is the pinentry issue: I haven't checked whether > gpg2.1 asking for passphrases on passphrase-less secure keys is to be > fixed on the gpg side. If yes, I would just wait for that since gpg2.1 > is not common yet. > > If not, we should provide (in gpg config) an alternative pinentry that > just returns an empty passphrase without bugging the user. Sounds like a sensible plan to me. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html