From: sebastian@krause.gnuu.de (Sebastian D.B. Krause)
Subject: [PGG] Make output more and less verbose
Date: Mon, 30 Dec 2002 00:14:38 +0100 [thread overview]
Message-ID: <87wulsfme9.fsf@sdbk.de> (raw)
Hi!
When I get an encrypted message, PGG's output is IMHO by default too
short, I don't get any information about the key which was used or
about the signature:
,----
| [[PGP Encrypted Part:OK]]
| foobar.
| [[End of PGP Encrypted Part]]
`----
It's annoying that I always have to press Enter on the bold text if
I want to get some more information (is there any way to let Gnus do
this automatically?). The second problem is that then there's *too*
much information I really don't need, the only interesting line are
the ones starting with "gpg:".
,----
| [[PGP Encrypted Part:OK]
| [GNUPG:] ENC_TO 829D6C175350A734 16 0
| [GNUPG:] USERID_HINT 829D6C175350A734 Sebastian D.B. Krause <krause@sdbk.de>
| [GNUPG:] NEED_PASSPHRASE 829D6C175350A734 CD81D83EC97CEC62 16 0
| [GNUPG:] GOOD_PASSPHRASE
| gpg: encrypted with 2048-bit ELG-E key, ID 5350A734, created 2002-08-29
| "Sebastian D.B. Krause <krause@sdbk.de>"
| [GNUPG:] BEGIN_DECRYPTION
| gpg: Signature made Sun Dec 29 23:58:56 2002 CET using DSA key ID C97CEC62
| [GNUPG:] SIG_ID ZFFMSke5BoQnTPNOdfBaLjga7AE 2002-12-29 1041202736
| [GNUPG:] GOODSIG CD81D83EC97CEC62 Sebastian D.B. Krause <krause@sdbk.de>
| gpg: Good signature from "Sebastian D.B. Krause <krause@sdbk.de>"
| [GNUPG:] VALIDSIG C0A4220174557BF6546DEE01CD81D83EC97CEC62 2002-12-29 1041202736 0
| [GNUPG:] TRUST_ULTIMATE
| [GNUPG:] DECRYPTION_OKAY
| [GNUPG:] GOODMDC
| [GNUPG:] END_DECRYPTION
| ]
`----
So, is there any way to get this output by default (*without*
pressing enter on the bold text)?
,----
| [[PGP Encrypted Part:OK]
| gpg: encrypted with 2048-bit ELG-E key, ID 5350A734, created 2002-08-29
| "Sebastian D.B. Krause <krause@sdbk.de>"
| gpg: Signature made Sun Dec 29 23:58:56 2002 CET using DSA key ID C97CEC62
| gpg: Good signature from "Sebastian D.B. Krause <krause@sdbk.de>"
| ]
`----
If not, could someone please write the code for it? :) Lisp is a
little too complicated for me to learn it in one day...
Sebastian
next reply other threads:[~2002-12-29 23:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-29 23:14 Sebastian D.B. Krause [this message]
2003-01-02 19:51 ` Lars Magne Ingebrigtsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wulsfme9.fsf@sdbk.de \
--to=sebastian@krause.gnuu.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).