295287 - No reply whit 2 certificat X509

Status: RESOLVED EXPIRED

(Thunderbird :: Security, defect)

Description

[Samuel MICHEL]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr-FR; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

First Sorry for my poor language :(
i use 2 certificate (x509v3) : 1 for sign and 1 for cypher (in a cardman)
In my cert8.db, i have the all cypher certificate.

I sends to B a signed and cypher e-mail ( 2certifcate !! )
If B see the e-mail before reply, TB dont find my certificate for cypher.

If i deactivate seeing (F8), restart, and use right clic to reply is ok !!! 
Bug is only when the mail is see before reply !!! 
I thing TB use the p7 in the first mail to cypher, but this in only for digital
signature.

Note :  if i forward to C in a signed and cypher e-mail, no prob :?

Reproducible: Always

Steps to Reproduce:
1. I sends to B a signed and cypher e-mail ( 2certifcate !! )
2. B reply a signed and cypher e-mail ( 2certifcate !! )
3. TB dont find the cypher certifate :(

Comment 1

[Samuel MICHEL]

"Sending of message failed.
You specified encryption... ...application falied to find an encryption
certificate for [my_email_address]."

Comment 2

[zug_treno]

Related to bug 292840? Maybe also related to Core bug 244321 (see Bob hits
'Reply' in Steps to Reproduce:)?

Comment 3

[Samuel MICHEL]

(In reply to comment #2)
> Related to bug 292840? Maybe also related to Core bug 244321 (see Bob hits
> 'Reply' in Steps to Reproduce:)?


Right same as bug 244321

BUT i found the prob exacly

the CN in the 2 certificat MUST BE defferent

Example

My name is Samuel MICHEL

my DN in the cypher certicate is  E=[e-mail], cn=Samuel MICHEL, DC=... ...

My DN in the sign certicate is idem

If i make cypher certificate whit cn=cypher, the prob is end

SO I U HAVE 2 CERTIFICAT USE DIFFENTE CN !!!!

Comment 4

[Gervase Markham [:gerv]]

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/

Comment 5

[Gervase Markham [:gerv]]

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.