Version info from previous post: CentOS release 6.8 (Final) gpg (GnuPG) 2.0.14
CentOS Linux release 7.3.1611 (Core) gpg (GnuPG) 2.0.22 We are NOT using pinentry. On Mon, Apr 17, 2017 at 1:37 PM, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote: > On Wed 2017-04-12 11:02:04 -0500, helices wrote: > > Yes, I saw that. On one host, that works. > > > > On other, I get following error: > > gpg> passwd > > Key is protected. > > > > You need a passphrase to unlock the secret key for > > user: "Sempris <public...@sempris.com>" > > 4096-bit RSA key, ID 80167A71, created 2016-03-18 > > > > gpg: cancelled by user > > Can't edit this key: Operation cancelled > > We need more info about the host where this failed to help you :) > > * What operating system? (and what version of the OS?) > > * What version of gpg? > > * What version of pinentry are you expecting to use? > > * If you do the following command from the shell, do you see a pinentry > show up anywhere? > > printf "option ttyname $(tty)\ngetpin\n" | pinentry > > Regards, > > --dkg >
_______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
