Summary | Allow both PGP and/or S/MIME verification |
Queue | IMP |
Queue Version | HEAD |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | selsky (at) columbia (dot) edu |
Created | 02/15/2006 (7054 days ago) |
Due | |
Updated | 03/02/2006 (7039 days ago) |
Assigned | |
Resolved | 03/02/2006 (7039 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
be scanned for PGP data?' selected then. The PGP signature
information is not PGP/MIME compliant so it won't happen unless that
option is set. This message verifies successfully with both protocols
in HEAD.
New Attachment: Advisory_ Internet Explorer Drag and Drop Redeux _CVE-2005-3240_ _fwd.eml
State ⇒ Feedback
no sense at all - if you do multiple signing it has to be either PGP
or SMIME not both
multipart/signed part must contain a 'protocol' parameter. And this
protocol parameter must be either PGP or S/MIME, not both. The only
example I can think of would be as follows:
multipart/signed - PGP
[pgp header data]
multipart/signed - SMIME encryption
[data]
[end] multipart/signed - SMIME
[end]
this message would be completely pointless since there is no reason to
encrypt an already encrypted message (or sign an already signed
message, etc.) Anyway, if we can't handle this data then this is an
issue e.g.
Bug 1866anyway.no sense at all - if you do multiple signing it has to be either PGP
or SMIME not both
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Allow both PGP and/or S/MIME verification
Queue ⇒ IMP
given the option of verifying the message using S/MIME. PGP
verification should be done as well.