unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Werner Koch <wk@gnupg.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Possible GPG bugs or misfeatures
Date: Tue, 01 Mar 2005 12:14:37 +0100	[thread overview]
Message-ID: <87vf8blisi.fsf@wheatstone.g10code.de> (raw)
In-Reply-To: <E1D5spt-0005ON-0b@fencepost.gnu.org> (Richard Stallman's message of "Mon, 28 Feb 2005 16:53:53 -0500")

Hi!

Your mail has been forwarded to me.

> From: "Luedde, Mirko" <mirko.luedde@sap.com>

> * the `--verify' option can be combined with `--output', but the
>   latter has no effect.=20

--verify does not output the message itself.  If you need that, you
should call gpg without --verifty.  The default is to verify or
decrypt the message.

> * the `--decrypt' option can be applied to signed but unencrypted
>   files and strips the signature from the file. however, if the file
>   is corrupted, gpg will not notice that the signature does not match
>   the content.

Just did a test and I either can't replicate that or I did not
understand the problem:

  $ gpg --decrypt <x.asc
  Linux wheatstone 6.0.0 #9 Sun Mar 1 15:15:11 CET 2005 i686 GNU/Linux
  
  The programs included with the Debian GNU/Linux system are free software;
  the exact distribution terms for each program are described in the
  individual files in /usr/share/doc/*/copyright.
  
  Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
  permitted by applicable law.
  gpg: Signature made Tue Mar  1 12:01:22 2005 CET using DSA key ID 010A57ED
  gpg: please do a --check-trustdb
  gpg: BAD signature from "Werner Koch <wk@gnupg.org>"

I created the message using

   gpg --clearsign </etc/motd >x.asc

and modified it. Same when using binary signatures.


Salam-Shalom,

   Werner

           reply	other threads:[~2005-03-01 11:14 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <E1D5spt-0005ON-0b@fencepost.gnu.org>]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vf8blisi.fsf@wheatstone.g10code.de \
    --to=wk@gnupg.org \
    --cc=bug-gnu-emacs@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).