Gnus development mailing list
 help / color / mirror / Atom feed
From: Ivan Boldyrev <boldyrev+nospam@cgitftp.uiggm.nsc.ru>
Subject: Re: Problem with signature verification using PGG
Date: Sat, 26 Jul 2003 15:03:33 +0700	[thread overview]
Message-ID: <l7p9vxj82.ln2@elaleph.borges.cgitftp.uiggm.nsc.ru> (raw)
In-Reply-To: <86u19aao3p.fsf@thirst.corponet.era.pl>

On 8450 day of my life Sławek Żak wrote:

>   zedek> Furthermore I am almost sure we can give you a quick dirty
>   zedek> hack to fix this temporaly at least ;)
>
> That could do :) Nevertheles I wonder why the MIME headers are verified along
> with the message.

RFC 3156:

   (5)   As described in [2], the digital signature MUST be calculated
         over both the data to be signed and its set of content headers.
              ^^^^     ^^^^              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[2] is RFC 1847.

-- 
Ivan Boldyrev

                                       XML -- new language of ML family.




  reply	other threads:[~2003-07-26  8:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-22 16:59 Sławek Żak
2003-07-24 17:17 ` Xavier Maillard
2003-07-25 10:37   ` Sławek Żak
2003-07-26  8:03     ` Ivan Boldyrev [this message]
2003-07-31  1:01 ` 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=l7p9vxj82.ln2@elaleph.borges.cgitftp.uiggm.nsc.ru \
    --to=boldyrev+nospam@cgitftp.uiggm.nsc.ru \
    /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).