Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Marshall T. Vandegrift <vandem2@rpi.edu>
Subject: Re: Bad PGP signatures due to MIME encoding (?)
Date: Thu, 17 Apr 2003 08:37:04 -0400	[thread overview]
Message-ID: <871y01711r.fsf@rpi.edu> (raw)
In-Reply-To: <87adep71q4.fsf@rpi.edu>

[-- Attachment #1: Type: text/plain, Size: 207 bytes --]

<much ugliness cut>

Heh.  That was pretty.  PGP and MIME don't mix?  One must use PGP/MIME
to sign multipart message?  Let's try again, and in the interest of
safety I'll just leave this message unsigned:


[-- Attachment #2: locally archived message --]
[-- Type: text/plain, Size: 2817 bytes --]

X-From-Line: nobody Wed Apr 16 22:31:17 2003
To: ding@hpc.uh.edu
Subject: Re: [PGG] Any way to download keys automatically?
From: Marshall T. Vandegrift <vandem2@rpi.edu>
Date: Wed, 16 Apr 2003 22:31:05 -0400
In-Reply-To: <877k9tevry.fsf@pooh.honeypot.net> (Kirk Strauser's message of
 "Wed, 16 Apr 2003 20:51:29 -0500")
Message-ID: <87smsh7t3q.fsf@rpi.edu>
User-Agent: Gnus/5.090018 (Oort Gnus v0.18) Emacs/21.3 (gnu/linux)
X-Draft-From: ("nnml:mail.list.gnus.ding" 169)
References: <87adepew4g.fsf@egil.codesourcery.com>
	<877k9tevry.fsf@pooh.honeypot.net>
Face:  iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEUAAACrq6tpaWnU1NSO
 jo7///9ISEgoKCit8pKhAAACWElEQVR4nHWTQW/bMAyFiWGIz4rV7bqwgnJ2ZPcuR0jOmZF7
 KwTUNcgG6+/vMWmLtsiYi8FPj3okFTr+J+jD98YN90Ev+eEumJZyuguOYelXd8Fx6nl1Fxwn
 M27vgsPQ8cNXME0hhOEY4heAZJiCeWvlHXTboLHcfgGTaQdV7E7DZ9DHqyDs5JOrqbNmUkXn
 5VVyA51N7VUAIB/sBusS6sNWLyKP72AwCQDpEDZS5GV4BVOXmBmXTwpETu0NHDyzc445oZMf
 UkpO4QZKnasIaDJwK5J5OyjAeqrAFAqNzhcpeVyFq2IUmTliet0u4xMKp2BKLHKulwhTOCLz
 DIBjdGCAsmjyNrRjlloBGNdTryCbc15htKptYMRtj7RhTMF1+5MJoffjTyIPh3GgUQAeu+UL
 bHXMnha4CLVIBbntUsRwTSw7musMSSKfs3BsnU4Xs9lRUZAZAKbqhQE6E5f7qgBnUcoLycVG
 Y0wXzR6GRbzPNHIGyO4KbLuv6EQHpqUKiWMFpg27c3MlmVh8oepytFfyhBZRrAjhCqEqczYW
 v7DhoqQKYQO+1Cx/jU3JmD760uj9GACizOKQj234nZbropMkzctzTti7i+0wmuRlrgWuSini
 q2TPzoTDCRUZS0EL86zZM814BIf1ylo7YsFCpczYM1FzSe3xqTHGxqSbpDWm+UxECxuG6fzd
 JAsXrK5qOZMGXuaeVmgGZNT51VuevoUlNS4lG6NKMH56DXws8OoQKoGr8xuhJmfG+04qQR+3
 5Ez0Hf+Om0RBWqui1l9Ef/pRTo5HF1HsH5ecMp4LrZOPAAAAAElFTkSuQmCC
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
Lines: 41
Xref: tiktok mail.sent:481
X-Gnus-Article-Number: 481   Wed Apr 16 22:31:17 2003

--=-=-=
Content-Transfer-Encoding: quoted-printable

Kirk Strauser <kirk@strauser.com> writes:

> Edit your ~/.gnupg/options.  Add:
>
>    keyserver-options auto-key-retrieve

It's `~/.gnupg/gpg.conf' these days (as of version 1.1.92), but yes.
However, PGG does also include support to retrieve keys itself:

,----[ C-h v pgg-query-keyserver ]
| pgg-query-keyserver's value is nil
|=20
| Documentation:
| Whether PGG queries keyservers for missing keys when verifying messages.
`----

Does this exist for OpenPGP implementations which do not support
automated key-retrieval, or is there some good reason to have PGG do
it instead of the OpenPGP tool?

=2D-=20
Marshall T. Vandegrift <vandem2@rpi.edu>

They were all, one might say, nonexistent, but each
non-existed in an entirely different way.
        -- Stanislaw Lem, /The Cyberiad/

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+nhH0aQb6rnTjFokRAkE9AJwN5zSlLuSADoAP/uQ2OQZ9VwEG2gCffyiW
P8Dbe9Bphtj93dcAxisCAJc=
=IhU3
-----END PGP SIGNATURE-----
--=-=-=--

[-- Attachment #3: mailing-list received message --]
[-- Type: text/plain, Size: 4168 bytes --]

Path: main.gmane.org!not-for-mail
From: "Marshall T. Vandegrift" <vandem2@rpi.edu>
Newsgroups: gmane.emacs.gnus.general
Subject: Re: [PGG] Any way to download keys automatically?
Date: Wed, 16 Apr 2003 22:31:05 -0400
Lines: 43
Sender: ding-owner@lists.math.uh.edu
Approved: news@gmane.org
Message-ID: <87smsh7t3q.fsf@rpi.edu>
References: <87adepew4g.fsf@egil.codesourcery.com>
	<877k9tevry.fsf@pooh.honeypot.net>
NNTP-Posting-Host: main.gmane.org
Mime-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-=";
	micalg=pgp-sha1; protocol="application/pgp-signature"
X-Trace: main.gmane.org 1050546677 6287 80.91.224.249 (17 Apr 2003 02:31:17 GMT)
X-Complaints-To: usenet@main.gmane.org
NNTP-Posting-Date: Thu, 17 Apr 2003 02:31:17 +0000 (UTC)
Original-X-From: ding-owner+M97@lists.math.uh.edu Thu Apr 17 04:31:14 2003
Return-path: <ding-owner+M97@lists.math.uh.edu>
Original-Received: from malifon.math.uh.edu ([129.7.128.13])
	by main.gmane.org with esmtp (Exim 3.35 #1 (Debian))
	id 195zBB-0001d7-00
	for <ding-account@gmane.org>; Thu, 17 Apr 2003 04:31:13 +0200
Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu)
	by malifon.math.uh.edu with smtp (Exim 3.20 #1)
	id 195zBl-0004A1-00; Wed, 16 Apr 2003 21:31:49 -0500
Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=root)
	by malifon.math.uh.edu with esmtp (Exim 3.20 #1)
	id 195zBd-00049v-00
	for ding@lists.math.uh.edu; Wed, 16 Apr 2003 21:31:41 -0500
Original-Received: from tiktok (alb-24-194-32-10.nycap.rr.com [24.194.32.10])
	by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id VAA28921
	for <ding@hpc.uh.edu>; Wed, 16 Apr 2003 21:32:49 -0500 (CDT)
Original-Received: from llasram by tiktok with local (Exim 4.12)
	id 195zBE-00011U-00
	for ding@hpc.uh.edu; Wed, 16 Apr 2003 22:31:16 -0400
Original-To: ding@hpc.uh.edu
In-Reply-To: <877k9tevry.fsf@pooh.honeypot.net> (Kirk Strauser's message of
 "Wed, 16 Apr 2003 20:51:29 -0500")
User-Agent: Gnus/5.090018 (Oort Gnus v0.18) Emacs/21.3 (gnu/linux)
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEUAAACrq6tpaWnU1NSO
 jo7///9ISEgoKCit8pKhAAACWElEQVR4nHWTQW/bMAyFiWGIz4rV7bqwgnJ2ZPcuR0jOmZF7
 KwTUNcgG6+/vMWmLtsiYi8FPj3okFTr+J+jD98YN90Ev+eEumJZyuguOYelXd8Fx6nl1Fxwn
 M27vgsPQ8cNXME0hhOEY4heAZJiCeWvlHXTboLHcfgGTaQdV7E7DZ9DHqyDs5JOrqbNmUkXn
 5VVyA51N7VUAIB/sBusS6sNWLyKP72AwCQDpEDZS5GV4BVOXmBmXTwpETu0NHDyzc445oZMf
 UkpO4QZKnasIaDJwK5J5OyjAeqrAFAqNzhcpeVyFq2IUmTliet0u4xMKp2BKLHKulwhTOCLz
 DIBjdGCAsmjyNrRjlloBGNdTryCbc15htKptYMRtj7RhTMF1+5MJoffjTyIPh3GgUQAeu+UL
 bHXMnha4CLVIBbntUsRwTSw7musMSSKfs3BsnU4Xs9lRUZAZAKbqhQE6E5f7qgBnUcoLycVG
 Y0wXzR6GRbzPNHIGyO4KbLuv6EQHpqUKiWMFpg27c3MlmVh8oepytFfyhBZRrAjhCqEqczYW
 v7DhoqQKYQO+1Cx/jU3JmD760uj9GACizOKQj234nZbropMkzctzTti7i+0wmuRlrgWuSini
 q2TPzoTDCRUZS0EL86zZM814BIf1ylo7YsFCpczYM1FzSe3xqTHGxqSbpDWm+UxECxuG6fzd
 JAsXrK5qOZMGXuaeVmgGZNT51VuevoUlNS4lG6NKMH56DXws8OoQKoGr8xuhJmfG+04qQR+3
 5Ez0Hf+Om0RBWqui1l9Ef/pRTo5HF1HsH5ecMp4LrZOPAAAAAElFTkSuQmCC
Precedence: bulk
Xref: main.gmane.org gmane.emacs.gnus.general:51553
X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:51553

--=-=-=
Content-Transfer-Encoding: quoted-printable

Kirk Strauser <kirk@strauser.com> writes:

> Edit your ~/.gnupg/options.  Add:
>
>    keyserver-options auto-key-retrieve

It's `~/.gnupg/gpg.conf' these days (as of version 1.1.92), but yes.
However, PGG does also include support to retrieve keys itself:

,----[ C-h v pgg-query-keyserver ]
| pgg-query-keyserver's value is nil
|=20
| Documentation:
| Whether PGG queries keyservers for missing keys when verifying messages.
`----

Does this exist for OpenPGP implementations which do not support
automated key-retrieval, or is there some good reason to have PGG do
it instead of the OpenPGP tool?

--=20
Marshall T. Vandegrift <vandem2@rpi.edu>

They were all, one might say, nonexistent, but each
non-existed in an entirely different way.
        -- Stanislaw Lem, /The Cyberiad/

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA+nhH0aQb6rnTjFokRAkE9AJ9ghVQPJjlccOWpDOwlbamXP+ZtBQCfUBYP
z37pvXlrurm82wL5Rvulxeg=
=I/AB
-----END PGP SIGNATURE-----
--=-=-=--



[-- Attachment #4: Type: text/plain, Size: 219 bytes --]


-- 
Marshall T. Vandegrift <vandem2@rpi.edu>

Disciplined and calm, to await the appearance of
disorder and hubbub amongst the enemy:--this is the
art of retaining self-possession.
        -- Sun Tzu, /The Art of War/

  reply	other threads:[~2003-04-17 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87istd7s2v.fsf@rpi.edu>
     [not found] ` <iluu1cxpcq8.fsf@latte.josefsson.org>
2003-04-17 12:22   ` Marshall T. Vandegrift
2003-04-17 12:37     ` Marshall T. Vandegrift [this message]
     [not found] ` <iluhe8wm9b0.fsf@latte.josefsson.org>
     [not found]   ` <87vfxc9dlb.fsf@rpi.edu>
     [not found]     ` <iluistbor34.fsf@latte.josefsson.org>
2003-04-18 15:12       ` Marshall T. Vandegrift
     [not found]         ` <iluznmnn3dk.fsf@latte.josefsson.org>
     [not found]           ` <87he8vf801.fsf@rpi.edu>
2003-04-19 12:49             ` 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=871y01711r.fsf@rpi.edu \
    --to=vandem2@rpi.edu \
    /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).