Gnus development mailing list
 help / color / mirror / Atom feed
From: jam@jamux.com (John A. Martin)
Subject: Re: pgg doesn't seem to like me
Date: Wed, 02 Oct 2002 14:36:30 -0400	[thread overview]
Message-ID: <873croy9g1.fsf@athene.jamux.com> (raw)
In-Reply-To: <874rc57u6e.fsf@mail.paradoxical.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Using cvs gnus gotten about 14:30 GMT 1 Oct atop XEmacs21
(xemacs21-nomule_21.4.6-8_i386.deb and friends) after checking
load-path (locate-library "pgg") and with ~/.gnus containing, in part:

        (require 'pgg)
        (mml-signencrypt-style "pgpmime" 'combined)

I found no suprize reading a message composed with C-c C-m s p
(mml-secure-message-sign-pgpmime).  However, when using C-c C-m c p
(mml-secure-message-encrypt-pgpmime) without an argument and
decrypting I see, in the Article buffer,

- --8<---------------cut here---------------start------------->8---
From: jam@jamux.com (John A. Martin)
Subject: pgp/mime encrypt
To: jam@jamux.com
Date: Wed, 02 Oct 2002 12:51:28 -0400

Content-Transfer-Encoding: quoted-printable

Use gnus not guns!


- --8<---------------cut here---------------end--------------->8---

and in the minibuffer,

        Unknown encoding quoted-printable\r; defaulting to 8bit

The *MML2015 Result* buffer contains

- --8<---------------cut here---------------start------------->8---
[GNUPG:] ENC_TO 605637744FC125AD 16 0
[GNUPG:] USERID_HINT 605637744FC125AD John A. Martin <jam@jamux.com>
[GNUPG:] NEED_PASSPHRASE 605637744FC125AD 504BEFD5BFE25F2F 16 0
[GNUPG:] GOOD_PASSPHRASE
gpg: encrypted with 1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19
      "John A. Martin <jam@jamux.com>"
[GNUPG:] BEGIN_DECRYPTION
[GNUPG:] DECRYPTION_OKAY
[GNUPG:] GOODMDC
[GNUPG:] END_DECRYPTION
- --8<---------------cut here---------------end--------------->8---

Decrypting the message from the command line gives:

- --8<---------------cut here---------------start------------->8---
$ cat ~/Mail/t-test/46|gpg 

You need a passphrase to unlock the secret key for
user: "John A. Martin <jam@jamux.com>"
1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19 (main key ID BFE25F2F)

gpg: encrypted with 1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19
      "John A. Martin <jam@jamux.com>"
Content-Transfer-Encoding: quoted-printable

Use gnus not guns!


- --8<---------------cut here---------------end--------------->8---

Where I would have expected something more like

- --8<---------------cut here---------------start------------->8---
$ echo Use gnus not guns\!|gpg -seatr jam@jamux.com|gpg

You need a passphrase to unlock the secret key for
user: "John A. Martin <jam@jamux.com>"
1024-bit DSA key, ID BFE25F2F, created 1998-09-19

gpg: jam@jamux.com: skipped: public key already present

You need a passphrase to unlock the secret key for
user: "John A. Martin <jam@jamux.com>"
1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19 (main key ID BFE25F2F)

gpg: encrypted with 1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19
      "John A. Martin <jam@jamux.com>"
Use gnus not guns!
gpg: Signature made Wed Oct  2 14:00:00 2002 EDT using DSA key ID BFE25F2F
gpg: Good signature from "John A. Martin <jam@jamux.com>"
gpg:                 aka "John A. Martin <jam@acm.org>"
- --8<---------------cut here---------------end--------------->8---

showing that the encrypted message had been signed.

Does it look like two problems: (1) some encoding/decoding mixup, and
(2) the encrypted message is not signed.

When I do C-u C-c C-m c p the decrypted article buffer looks like

- --8<---------------cut here---------------start------------->8---
From: jam@jamux.com (John A. Martin)
Subject: pgp/mime encrypt with argument
To: jam@jamux.com
Date: Wed, 02 Oct 2002 14:09:14 -0400


Use gnus not guns!
- --8<---------------cut here---------------end--------------->8---

with less cruft but still ugly, and no "mime heder".  Nothing in the
minibuffer and the *MML2015 Result* buffer is the same as above.  The
command line decription looks like this:

- --8<---------------cut here---------------start------------->8---
$ cat ~/Mail/t-test/47|gpg             

You need a passphrase to unlock the secret key for
user: "John A. Martin <jam@jamux.com>"
1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19 (main key ID BFE25F2F)

gpg: encrypted with 1024-bit ELG-E key, ID 4FC125AD, created 1998-09-19
      "John A. Martin <jam@jamux.com>"

Use gnus not guns!
- --8<---------------cut here---------------end--------------->8---

I dunno about this here except that gnus shows `^M' cruft that gpg on
the command line does not.

        jam

C-c / s

-----BEGIN PGP SIGNATURE-----

iD8DBQE9mzxvUEvv1b/iXy8RAm7sAJwJy6UwoPZnCUQGdrQDznIKqQTnKwCdHT8i
RwFZc22AgeUISr2cgnWbBE4=
=J0mS
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2002-10-02 18:36 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01 17:27 John A. Martin
2002-10-01 18:56 ` John A. Martin
2002-10-01 19:16   ` Josh Huber
2002-10-01 20:11     ` John A. Martin
2002-10-01 20:58       ` Josh Huber
2002-10-01 21:21         ` John A. Martin
2002-10-01 21:38           ` Josh Huber
2002-10-01 21:50             ` Jesper Harder
2002-10-01 23:32             ` John A. Martin
2002-10-02 18:36         ` John A. Martin [this message]
2002-10-02 19:20           ` John A. Martin
2002-10-03  0:22             ` Clemens Fischer
2002-10-03 23:00           ` Simon Josefsson
2002-10-03 23:04             ` Simon Josefsson
2002-10-05  4:45               ` John A. Martin
2002-10-05 11:24                 ` Simon Josefsson
2002-10-05 15:12                   ` John A. Martin
2002-10-05 21:22                     ` Raymond Scholz
2002-10-06  0:03                       ` Simon Josefsson
2002-10-06 10:14                         ` Raymond Scholz
2002-10-09 21:59                           ` Simon Josefsson
2002-10-10  0:15                             ` Simon Josefsson
2002-10-10 17:36                               ` Raymond Scholz
2002-10-06 19:46                         ` John A. Martin
2002-10-10  0:13                           ` Simon Josefsson
2002-10-10  4:55                             ` John A. Martin
2002-10-10 14:18                               ` Josh Huber
2002-10-10 15:18                               ` Simon Josefsson
2002-10-10 14:55                             ` John A. Martin
2002-10-10 15:54                               ` Simon Josefsson
2002-10-07 16:23                         ` Andreas Fuchs
2002-10-07 23:58                           ` Clemens Fischer
2002-10-10  0:34                             ` Simon Josefsson
2002-10-10  0:32                           ` Simon Josefsson
2002-10-10 10:42                             ` Andreas Fuchs
2002-10-10 15:00                               ` Simon Josefsson
2002-10-10 18:28                                 ` Andreas Fuchs
2002-10-10 23:24                                   ` Simon Josefsson
2002-10-08  2:11                         ` John A. Martin
2002-10-10  0:42                           ` Simon Josefsson
2002-10-08 13:37                         ` John A. Martin
2002-10-08 14:18                           ` Simon Josefsson
     [not found]             ` <gd.y1yr8f6yp8y.fsf@fly.verified.de>
     [not found]               ` <iluofa94z60.fsf@latte.josefsson.org>
2002-10-05 11:58                 ` Raymond Scholz
2002-10-05 14:17                   ` John A. Martin
2002-10-05 21:21                     ` Raymond Scholz
2002-10-01 22:54 ` Simon Josefsson

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=873croy9g1.fsf@athene.jamux.com \
    --to=jam@jamux.com \
    /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).