[Bug 190294] Re: gpg spams the terminal with passphrase message

[Thijs Kinkhorst]

--batch is indeed the intended way to go here. Discussion with upstream
concluded that it's just not worth fixing the case where --batch is left
out.

** Changed in: gnupg (Ubuntu)
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gnupg in Ubuntu.
https://bugs.launchpad.net/bugs/190294

Title:
  gpg spams the terminal with passphrase message

Status in GNU Privacy Guard:
  Confirmed
Status in “gnupg” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: gnupg

  For some reason gpg insists on spamming the console with this useless message:
  -------
  $ gpg --quiet --no-use-agent --sign --passphrase XXX -u "YYY" --output SIG FILE &> /dev/null

  You need a passphrase to unlock the secret key for
  user: "YYY"
  1024-bit DSA key, ID FFD40F72, created 2007-12-01

  --------
  This is despite the fact that:
  a) the passphrase is given on the command line (yeah, I know, it's OK here)
  b) I told it to be quiet
  c) I told it not to use the agent
  d) I redirected both outputs to /dev/null
  e) it doesn't actually _ask_ for the password (see point a) and the signing works.

  I don't even know _how_ it does that with the outputs redirected.
  Anyway, this is really annoying in scripts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnupg/+bug/190294/+subscriptions