337517 - OCSP: Can not send encrypted message with OCSP enabled

Status: RESOLVED WORKSFORME

(MailNews Core :: Security: S/MIME, defect, P1)

Description

[Kai Engert (:KaiE:)]

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.

Comment 1

[Kai Engert (:KaiE:)]

*** Bug 338613 has been marked as a duplicate of this bug. ***

Comment 2

[Darin Fisher]

Not going to block 1.8.1 for OCSP, but we'd definitely welcome low-risk patches.

Comment 3

[Kai Engert (:KaiE:)]

When working on this issue, we should address bug 353542 and bug 353544 at the same time.

Comment 4

[Kai Engert (:KaiE:)]

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.

Comment 5

[Kai Engert (:KaiE:)]

Problem on 1.8 branch (FF2) only.

Comment 6

[kraynopp]

Even simple signed message is not possible to send until clearing the certificate for encryption.

Comment 7

[Kai Engert (:KaiE:)]

According to my testing, this appears to work in Thunderbird 17.

This could have been fixed by the changes from bug 674147.

Comment 8

[Wayne Mery (:wsmwk)]

(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