Gnus development mailing list
 help / color / mirror / Atom feed
From: "Łukasz Stelmach" <stlman@poczta.fm>
To: ding@gnus.org
Subject: Re: [BUG] mml2015-epg-find-usable-key finds unusable key
Date: Sat, 16 Feb 2013 22:11:03 +0100	[thread overview]
Message-ID: <871ucg6k2g.fsf%stlman@poczta.fm> (raw)
In-Reply-To: <87bobk85tv.fsf%stlman@poczta.fm>

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

Daiki Ueno <ueno@gnu.org> writes:

> Łukasz Stelmach <stlman@poczta.fm> writes:
>
>> The patch needed a fix: there was a space before tab and my name for the
>> changelog has been messed up (maybe due to encoding issues?).
>
> Perhaps it is because I didn't use attachment, but just inserted the
> patch into the mail.  It will be fixed in the git commit.
>
>> There are two more issues:
>>
>> 1. mml2015-find-usable-key is called from
>> mml2015-epg-find-usable-secret-key. Your patch hasn't changed the
>> invocation.
>
> Oops, right.  Thanks for pointing this out.
>
>> 2. IMHO mml2015-epg-check-user-id should return true if a key id is
>> passed as a uid to check. I assume that if a caller passes id to
>> mml2015-find-usable-key find
>
> Yes,
>
>> +	    (string-match
>> +	     "^\\(0x\\)?[[:xdigit:]]\\{8\\}\\([[:xdigit:]]\\{8\\}\\)?$"
>> +	     recipient))
>
> I think this can be simplified to:
>
> (not (string-match "\\`<" recipient))
>
> since all the mml2015-epg-* functions normalize recipient addresses in
> the form of "<foo@bar>", so they only match email addresses.

Indeed, however I still think we should check this the hard way: return
t if and *only* if it is a key-id. The simpler check *might* result in
information disclosure if a message is encrypted to a revoked uid.

PS. This is a followup to some direct e-mails.
-- 
Miłego dnia,
Łukasz

[-- Attachment #2: Type: application/pgp-signature, Size: 619 bytes --]

  reply	other threads:[~2013-02-16 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 19:55 Łukasz Stelmach
2013-02-14 19:28 ` Łukasz Stelmach
2013-02-15  4:05 ` Daiki Ueno
2013-02-15  7:59   ` Łukasz Stelmach
2013-02-15  9:14     ` Daiki Ueno
2013-02-16 18:35   ` Łukasz Stelmach
2013-02-16 21:11     ` Łukasz Stelmach [this message]
2013-02-17  3:12       ` Daiki Ueno
2013-02-17  7:47         ` Łukasz Stelmach
2013-02-17  9:02           ` Daiki Ueno
2013-02-17 10:20             ` Daiki Ueno
2013-02-17 21:29               ` Łukasz Stelmach

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=871ucg6k2g.fsf%stlman@poczta.fm \
    --to=stlman@poczta.fm \
    --cc=ding@gnus.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.
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).