Encrypted received mail doesn't show up even if proper X509v3 private key is present in TB cert keyring (pkcs#12 imported succesfully)

RESOLVED EXPIRED

Status

RESOLVED EXPIRED
15 years ago
13 years ago

People

(Reporter: luca.regoli, Assigned: mscott)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       
Build Identifier: 

Example: 
A sends to B a signed e-mail
B now has public key of A and can cypher msg back to A (I used LotusNotes
because I didn't know hof to do it with TB)
When i try to read such encrypted mail just the header is displaied. It seems
encription stops TB to extract smime.P7M content nothwithstanding TB had the
private key. I tried both with my own cert and with other friends. The CA issuer
is present and trusted in the TB keyring.

It seems to me more that TB isn't able to open up a PKCS#7 smime.p7m attachment
even if not cyphered but didn't try still this second thinking.

Reproducible: Always
Steps to Reproduce:
1. Load a PKCS#12 containing a valid X509V3 cert in the TB keyring
2. try to send signed mail to another person
3. this person have to store public key in NAB (address book) and try to reply
writing some text in the body and then cyphering and send mail.
4. When TB will receive it. It won't be able to watch the content.

Actual Results:  
No body is visible: no text or other attachments

Expected Results:  
The body should display text sent from sender and / or attachments.

I didn't use special themes and I don't use Enigmail.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.