[Gpg4win-users-en] pinentry asks the same password three times (Psi 0.13, three accounts with the same private key)

Werner Koch wk at gnupg.org
Wed Aug 19 17:55:44 CEST 2009


On Wed, 19 Aug 2009 15:36, kiav1976 at mail.ru said:

> Werner, I have ONE key, and tree accounts in Psi using this key. pinentry
> asks the same password three times.

You can enable debugging for gpg-agent and look at the logfile (--debug
1024 shouldbe sufficient).  Here is an example with stripped timestamps:

  gpg-agent[10780.9] DBG: <- GET_PASSPHRASE --data --repeat=0 --
    1DFED28E885CE98C170CEE80907B5D1640619DD0
    Invalid+passphrase;+please+try+again X
    Please+enter+the+passphrase+to+unlock+the+secret+key+for+
    the+OpenPGP+certificate:%0A%22Joe+Random+Hacker+(test
    +key+with+passphrase+%22x%22)+<joe at setq.org>%22%0A1024
    -bit+RSA+key,+ID+40619DD0,%0Acreated+2004-09-23+(main+key+ID+9CD9FD55).%0A
  gpg-agent[10780]: starting a new PIN Entry
  gpg-agent[10780]: DBG: connection to PIN entry established
  gpg-agent[10780.9] DBG: -> INQUIRE PINENTRY_LAUNCHED 3966
  gpg-agent[10780.9] DBG: <- END
  gpg-agent[10780.9] DBG: -> [Confidential data not shown]
  gpg-agent[10780.9] DBG: -> [Confidential data not shown]

GET_PASSPHRASE is the command gpg send to the gpg-agent.  In this case
gpg-agent figures that it has no cached passphrase with the cache-id
1DFED28E885CE98C170CEE80907B5D1640619DD0 and pops up the pinentry nd ask
for the passphrase.  In the above example I entered a bad passphrase
first, thus you see the "Invalid passphrase, try again" prompt.

  gpg-agent[10780.9] DBG: <- GET_PASSPHRASE --data --repeat=0 --
    1DFED28E885CE98C170CEE80907B5D1640619DD0 X X
    Please+enter+the+passphrase+to+unlock+the+secret+key+for+
    the+OpenPGP+certificate:%0A%22Joe+Random+Hacker+(test
    +key+with+passphrase+%22x%22)+<joe at setq.org>%22%0A1024-bit+
    RSA+key,+ID+40619DD0,%0Acreated+2004-09-23+(main+key+ID+9CD9FD55).%0A
  gpg-agent[10780.9] DBG: -> [Confidential data not shown]
  gpg-agent[10780.9] DBG: -> [Confidential data not shown]
  gpg-agent[10780.9] DBG: <- [EOF]
  
Here GET_PASSPHRASE is called again with the same cache-id and because
the passphrase is still in the cache the passphrase is retruned
immediately.



Salam-Shalom,

   Werner



-- 
Die Gedanken sind frei.  Auschnahme regelt ein Bundeschgesetz.




More information about the Gpg4win-users-en mailing list