Closed
Bug 337517
Opened 19 years ago
Closed 9 years ago
OCSP: Can not send encrypted message with OCSP enabled
Categories
(MailNews Core :: Security: S/MIME, defect, P1)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: KaiE, Assigned: KaiE)
References
(Blocks 1 open bug)
Details
(Keywords: regression, Whiteboard: [kerh-bra])
When OCSP is enabled in the mail application, and a receipient's email encryption cert specifies an OCSP responder, it is not possible to send an encrypted message.
The attempt to send such an message results in an error message:
"Tnternal failure - unable to complete OCSP operation"
The same error message is displayed when using "view security info" to display information about recipient certs.
The problem is similar to the issue already fixed in bug 329990.
|
Assignee | |
Updated•19 years ago
|
Flags: blocking1.8.1?
Priority: -- → P1
|
|
Assignee | |
Comment 1•19 years ago
|
||
*** Bug 338613 has been marked as a duplicate of this bug. ***
|
|
Assignee | |
Updated•19 years ago
|
Whiteboard: [kerh-bra]
|
||
Comment 2•18 years ago
|
||
Not going to block 1.8.1 for OCSP, but we'd definitely welcome low-risk patches.
Flags: blocking1.8.1? → blocking1.8.1-
|
|
Assignee | |
Comment 3•18 years ago
|
||
When working on this issue, we should address bug 353542 and bug 353544 at the same time.
Keywords: regression
|
|
Assignee | |
Comment 4•18 years ago
|
||
A solution for the trunk is available in bug 353597.
I do not have a low risk solution for the stable 1.8 branch at this time.
|
|
Assignee | |
Comment 5•18 years ago
|
||
Problem on 1.8 branch (FF2) only.
Summary: OCSP: Unwind S/Mime recipient cert verification from UI thread → OCSP: Can not send encrypted message with OCSP enabled
Version: Trunk → 1.8 Branch
|
||
Updated•18 years ago
|
QA Contact: s.mime
Even simple signed message is not possible to send until clearing the certificate for encryption.
|
|
Assignee | |
Comment 7•12 years ago
|
||
According to my testing, this appears to work in Thunderbird 17.
This could have been fixed by the changes from bug 674147.
|
||
Comment 8•9 years ago
|
||
(In reply to Kai Engert (:kaie) from comment #7)
> According to my testing, this appears to work in Thunderbird 17.
>
> This could have been fixed by the changes from bug 674147.
Thanks for the update
=> WFM per comment 7
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Target Milestone: mozilla1.8.1 → ---
You need to log in
before you can comment on or make changes to this bug.
Description
•