can't encrypt e-mail message with valid certificate

RESOLVED FIXED in mozilla1.8.1beta1

Status

MailNews Core
Security: S/MIME
P1
normal
RESOLVED FIXED
12 years ago
8 years ago

People

(Reporter: Adam Hauner, Assigned: kaie)

Tracking

({fixed1.8.0.5, fixed1.8.1, regression})

1.8 Branch
mozilla1.8.1beta1
x86
Windows XP
fixed1.8.0.5, fixed1.8.1, regression
Bug Flags:
blocking1.8.0.5 +

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [kerh-bra])

(Reporter)

Description

12 years ago
SeaMonkey/1.0/WXP
SeaMonkey1.1a/2006040204/WXP

I own valid personal certificate (for purposes Client, Server, Sign, Encrypt) as my fellows in work. I could easily send digitaly signed e-mail with my certificate, I could receive their encrypted e-mails with recognized and valid certificates and decrypt it, but when I wanna send message to one of them, I can't encrypt message, although his certificate is visible in Certificate Manager as valid and with same purposes.

In Message Security dialog, SeaMonkey displays recipient with Not Found status. I'm sending from address, respectively to address written in certificates, I'm using correct certificate for e-mail address.

Comment 1

12 years ago
So the certs of the people you mail to are listed under "Other People's" in the cert manager? Their cert includes their mail address in the Subject as "E = ..."?  What do they use to send S/MIME encrypted mail? Actually i cannot imagine what else could be wrong here, S/MIME works in general, so it's not like S/MIME is completely broken.
(Reporter)

Comment 2

12 years ago
Yes, their are listed under "Other People's" and their e-mail shows in column "E-mail". But no, in Certificate Viewer I can't see their e-mail address in Subject as "E = ", there are available only CN, OU, OU, O, C items. Their e-mail address is in Extensions / Certificate Subject Alt Name as "E-mail Address: ...@..."

Issuer of my and also of their certificates is PostSignum Qualified CA <http://www.postsignum.cz/>.
(Assignee)

Updated

12 years ago
Component: Security → Security
Product: Mozilla Application Suite → Core
QA Contact: seamonkey → toolkit
(Assignee)

Updated

12 years ago
Assignee: dveditz → kengert
Component: Security → Security: S/MIME
QA Contact: toolkit
(Reporter)

Comment 3

12 years ago
BTW my fellow is able to send encypted e-mail from Thunderbird 1.5 with same set of certificates.
(Assignee)

Comment 4

12 years ago
I hope this is the same as bug 335021, let's retest once that gets fixed.
Depends on: 335021
(Assignee)

Comment 5

11 years ago
A couple of days ago, the hotfix for bug 335021 was picked up by both Mozilla trunk and Mozilla 1.8 branch.

Using a current nightly trunk build or 1.8 branch build, could you please test and confirm this bug is now fixed?
Thanks
(Reporter)

Comment 6

11 years ago
I'm on holiday now, I'll hopefully test it on wednesday on SeaMonkey 1.8 build. Thanx for note.
(Reporter)

Comment 7

11 years ago
WFM with 2006052204/1.8-branch/SeaMonkey1.1a =)
Was hotfix picked up also for 1.8.0 branch?
(Assignee)

Comment 8

11 years ago
(In reply to comment #7)
> WFM with 2006052204/1.8-branch/SeaMonkey1.1a =)
> Was hotfix picked up also for 1.8.0 branch?

Not yet, I just requested approval for 1.8.0.5 in bug 335021.
(Assignee)

Comment 9

11 years ago
As Julien backed out the hotfix, we are now forced to invest the additional time to verify his other patch (in bug 335021) fixes the problem, too.

I think this should block the TB 1.8.0.5 release, as it is a regression.
Flags: blocking1.8.0.5?
Keywords: regression
Priority: -- → P1
Whiteboard: [kerh-bra]
Target Milestone: --- → mozilla1.8.1beta1
Flags: blocking1.8.0.5? → blocking1.8.0.5+
(Assignee)

Comment 10

11 years ago
This has been fixed on trunk and 1.8 branch with NSS-landing bug 340724.

For 1.8.0.5 I requested approval for the patch in bug 335021.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Keywords: fixed1.8.1
Resolution: --- → FIXED
(Assignee)

Comment 11

11 years ago
*** Bug 333455 has been marked as a duplicate of this bug. ***
(Assignee)

Updated

11 years ago
Keywords: fixed1.8.0.5

Updated

8 years ago
Component: Security: S/MIME → Security: S/MIME
Product: Core → MailNews Core
QA Contact: s.mime
You need to log in before you can comment on or make changes to this bug.