Re: Quieten gpg-agent output?

2012-01-11 Thread Werner Koch
On Tue, 10 Jan 2012 15:33, aaron.topo...@gmail.com said:

 The problem with Mutt, is the fact that when changing folders or accounts,
 it brefly flashes what is on the terminal behind Mutt, and that message
 appears a lot, seeing as though I'm storing my IMAP and SMTP passwords in

You should use the modern crypto implementaion of mutt.  You merely need
to add

  set crypt_use_gpgme

to ~/.muttrc.  This uses a now also 10 years old mode of mutt which far
better integrates crypto than the old command based one.

 How can I completely suppress that message? It doesn't appear to be writing
 to STDOUT (fd 1) or STDERR (fd 2). I guess I should run strace(1) on it,

 --no-tty

will suppress all TTY output completely.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Quieten gpg-agent output?

2012-01-11 Thread Aaron Toponce
On Wed, Jan 11, 2012 at 01:56:58PM +0100, Werner Koch wrote:
 You should use the modern crypto implementaion of mutt.  You merely need
 to add

   set crypt_use_gpgme

 to ~/.muttrc.  This uses a now also 10 years old mode of mutt which far
 better integrates crypto than the old command based one.

How does this differ from set pgp_use_gpg_agent, if any?

  --no-tty

 will suppress all TTY output completely.

Perfect. I searched for STDOUT, STDERR and the like in hopes of finding
the necessary docs, without reading the full gpg(1) manual. Didn't think of
tty. Thanks.

--
. o .   o . o   . . o   o . .   . o .
. . o   . o o   o . o   . o o   . . o
o o o   . o .   . o o   o o .   o o o


pgpwo506vjOQ9.pgp
Description: PGP signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Quieten gpg-agent output?

2012-01-11 Thread Werner Koch
On Wed, 11 Jan 2012 17:27, aaron.topo...@gmail.com said:

 How does this differ from set pgp_use_gpg_agent, if any?

I don't know this.  However it has nothing to do with the gpgme mode.
The advantage of the gpgme mode is that for example the key selection
process is much tighter integrated.  There are also a lot of other
goodies.


Salam-Shalom,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Quieten gpg-agent output?

2012-01-10 Thread Aaron Toponce
On Fri, Dec 16, 2011 at 03:07:59PM +0100, Werner Koch wrote:
 On Thu, 15 Dec 2011 18:47, li...@chrispoole.com said:
  Is there a better way to get rid of these errors?

 Yes, use gpg2.  Using gpg and gpg-agent is just a kludge.  gpg2 requires
 gpg-agent and thus we don't need those messages there anymore.

I'm glad this was posted recently, because I'm just not getting bothered by
them. I'm using Mutt for my mail, hooked into gpg2 and the gpg-agent. THe
agent is running, and the pinentry comes up asking for my passphrase,
however, I still see tho following:

% gpg2 -qd file.gpg

You need a passphrase to unlock the secret key for
user: Aaron Toponce aaron.topo...@gmail.com
1792-bit ELG key, ID E7D41E4B, created 2004-09-18 (main key ID
8086060F)

The problem with Mutt, is the fact that when changing folders or accounts,
it brefly flashes what is on the terminal behind Mutt, and that message
appears a lot, seeing as though I'm storing my IMAP and SMTP passwords in
an encrypted file, and having Mutt use gpg2 to decrypt them.

How can I completely suppress that message? It doesn't appear to be writing
to STDOUT (fd 1) or STDERR (fd 2). I guess I should run strace(1) on it,
and see what I get. Thought I'd hit the list anyway, for archiving, in case
a solution is found, and someone else is searching.

--
. o .   o . o   . . o   o . .   . o .
. . o   . o o   o . o   . o o   . . o
o o o   . o .   . o o   o o .   o o o


signature.asc
Description: Digital signature
___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Re: Quieten gpg-agent output?

2011-12-16 Thread Werner Koch
On Thu, 15 Dec 2011 18:47, li...@chrispoole.com said:

 Is there a better way to get rid of these errors?

Yes, use gpg2.  Using gpg and gpg-agent is just a kludge.  gpg2 requires
gpg-agent and thus we don't need those messages there anymore.


Salam-Shalom,

   Werner


-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users


Quieten gpg-agent output?

2011-12-15 Thread Chris Poole
Hi,

I start gpg-agent with the -q option to make it quiet.

I then run a script that executes gpg -qse ... on several files,
encrypting and signing them (quietly).

I still find output like this in my terminal window:

 You need a passphrase to unlock the secret key for
 user: Chris Poole ch...@chrispoole.com2048-bit DSA key, ID 7ED39159, 
 created 2010-12-11 (main key ID BAD248F9)

I assume that gpg is reporting this, and then it checks for a key held
by the agent, which it uses (everything works fine, it's just the
output that annoys me).

I could quiten gpg totally, by running gpg ... 21 /dev/null, but
then I'd also stop any genuine errors that gpg reports. (I run this
command manually, usually, so would see errors.)

Is there a better way to get rid of these errors?


Cheers

___
Gnupg-users mailing list
Gnupg-users@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users