From: Simon Josefsson <jas@extundo.com>
Subject: Re: pgpmime & sign: gnus requests wrong address
Date: Sun, 18 May 2003 18:08:02 +0200 [thread overview]
Message-ID: <iluaddkb5lp.fsf@latte-wlan.josefsson.org> (raw)
In-Reply-To: <86vfw82uk8.fsf@shadowprint.de>
Daniel Hofmann <usenet@shadowprint.de> writes:
> Simon Josefsson <jas@extundo.com> writes:
>
>> Daniel Hofmann <usenet@shadowprint.de> writes:
>>
>>> Hi,
>>>
>>> when I am trying to use a pgp/mime signature (secure method=pgpmime
>>> mode=sign), gnus asks for the wrong passphrase: for the systemuser I
>>> am logged in as, not the one according to the From: - field.
>>
>> Set `pgg-default-user-id' to your real user id. By default, it uses
>> whatever the OpenPGP implementation thinks is best, which may be
>> incorrect. Another solution is to specify a default key in the
>> OpenPGP implementation.
>>
>>> Using plain pgp (secure method=pgp mode=sign) works fine.
>>
>> This was a bug, will be fixed in the next release.
>>
>> The problem is that using From: as a source of key id is not reliable,
>> some people do not have a key id matching the From: address they use,
>> and this would force them to specify a MML sender= tag. Instead, Gnus
>> will in the future not assume anything about the key ID unless
>> specified by the user.
>>
>> Suggestions on this are welcome, it still isn't very mature.
>
> As I am handling several email - identities I found the bug with plain
> pgp was actually a feature. But I understand the trouble with it. Is
> there a way to handle different pgp user id's with
> gnus-posting-styles?
Have it insert a MML sender= tag corresponding to the user id you use?
Or bind a buffer local pgg-default-user-id to the right pgp user id?
parent reply other threads:[~2003-05-18 16:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <86vfw82uk8.fsf@shadowprint.de>]
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=iluaddkb5lp.fsf@latte-wlan.josefsson.org \
--to=jas@extundo.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).