Closed Bug 2052069 Opened 3 months ago Closed 1 month ago

S/MIME encrypted(signed) message not rendered

Categories

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

Thunderbird 154
defect

Tracking

(thunderbird_esr153 unaffected, thunderbird153 unaffected)

RESOLVED WORKSFORME
155 Branch
Tracking Status
thunderbird_esr153 --- unaffected
thunderbird153 --- unaffected

People

(Reporter: KaiE, Assigned: KaiE)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

The fix for bug 1946168 introduced a regression.

Start TB
Make sure that the first message that is clicked in the session is a message that is S/MIME encrypted and contains a S/MIME signature inside.

Actual behavior:
Message not rendered.

Expected behavior:
Message should be rendered.

I have a fix in hand and will submit it tomorrow.

Blocks: tb153found
Depends on: 2052995
Blocks: 2052070
Attachment #9603778 - Attachment description: Bug 2052069 - Ensure switching to the S/MIME handler for multipart/signed works. r=#thunderbird-back-end-reviewers → Bug 2052069 - Ensure switching to the S/MIME handler for multipart/signed works. r=tobyp

Doesn't affect 153 (unless we decide to uplift bug 1946168).

No longer blocks: tb153found
Blocks: tb153found
No longer blocks: tb153found

Pushed by kaie@kuix.de:
https://hg.mozilla.org/comm-central/rev/8519745d359e
Ensure switching to the S/MIME handler for multipart/signed works. r=tobyp

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 154 Branch

Because this was backed from beta 154, I'm changing the target milestone to 155.
https://hg-edge.mozilla.org/releases/comm-beta/rev/57a0a8513d30f538f6538b214dd5e34dc17c70a2

Target Milestone: 154 Branch → 155 Branch

I suggest to back out, together with bug 1946168

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Pushed by kaie@kuix.de:
https://hg.mozilla.org/comm-central/rev/ec53993ce917
Backed out changeset 3de4beeb246bcef7bad5126344e039ab596d66de. r=backout

Status: REOPENED → RESOLVED
Closed: 2 months ago → 1 month ago
Resolution: --- → FIXED

no, commit bot, this wasn't fixed, reopening.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---

The regression was fixed by backing out. No stable release had contained the regression, just beta.

Status: REOPENED → RESOLVED
Closed: 1 month ago → 1 month ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: