Closed Bug 1906487 Opened 1 year ago Closed 10 months ago

Root certification expiry - update to Fx128 to fix it

Categories

(support.mozilla.org :: Knowledge Base Content, task)

Product:
support.mozilla.org
Component:
Knowledge Base Content
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: vtay, Assigned: lsiebert)

References

Details

Did you check out the steps and FAQs for submitting requests to the CX content team? (yes or no)? [REQUIRED]

**Note: Learn more at https://mozilla-hub.atlassian.net/wiki/spaces/MSS/pages/21430745/Mozilla+Support+Content **
Yes

IMPORTANT NOTICE: FOR TIMELY PUBLICATION, CONTENT REQUESTS MUST BE SUBMITTED AT LEAST 14 DAYS BEFORE THE RELEASE DATE, ENABLING THE SUMO TEAM TO MAKE THEM LIVE WITHIN 48 HOURS POST-RELEASE. PLEASE ENSURE THAT ALL SUBMITTED INFORMATION, INCLUDING FEATURE DETAILS AND VISUAL ASSETS, IS FINAL. IN THE EVENT OF ANY UNFORESEEN CHANGES OR DELAYS NECESSITATING A PUSH TO A SUBSEQUENT RELEASE, PROMPTLY INFORM US TO PREVENT PUBLISHING AS PER THE ORIGINAL SCHEDULE.

Is the content restricted to staff or under embargo (yes or no)? [REQUIRED]

No.

Product (ensure to select only one product for each ticket. If your request involves multiple products, file an individual Bugzilla for each)

Choose one below and delete others. [REQUIRED]
Firefox for Desktop (Windows)
Firefox for Desktop (macOS)
Firefox for Desktop (Linux)
Firefox for Android

Select the type of request.

Choose one or more below and delete others. [REQUIRED]
KB new content
In product link

Please provide a summary of the request and outline any user-facing changes. [REQUIRED]

On March 14, 2025, a root certificate used for verifying signed content and add-ons in multiple Mozilla projects – including Firefox – will expire. Without effort ahead of time, the expiration will trigger another very bad “Armag-add-on”.

Remote settings would no longer be updatable, installed add-ons would be disabled, prevent the GMP add-on updates (and so prevent DRM’ed content from playing in user devices), and a variety of other systems that happen to use content signing under the hood would stop working for users.

This is fixable if a user updates to Fx128 + ( or ESR 115.13+ for Windows 7/8/8.1 users).

Starting from September 2024, we will be messaging users with Firefox versions below Fx128 to update.

Are the user-facing changes mentioned above final? (yes or no)? [REQUIRED]

Yes.

Is this an on- or off-train release? Please indicate the product version number, if applicable, and add it to the end of the Summary field using the format of: Summary [Product V123]. [REQUIRED]

We should time the SUMO article to come out at the same time as the first message - September 2024.

What is the anticipated release date? [REQUIRED]

Note: Content is typically published at, or within, 48 hours of the release.
September 2024

Does the content need to be published prior to the release date? If so, when? [REQUIRED]

Note: If you don’t let us know if this date changes, it will be published on this date
NO.

Does the content need to be localized in any languages outside of EN-US? If yes, please indicate which languages. [REQUIRED]

Note: A minimum of 10 days is required for translation requests.
All languages

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

https://mozilla-hub.atlassian.net/wiki/spaces/IP/pages/630948678/Content+Signing+Certificate+Succession+Project
https://docs.google.com/document/d/1iiewAZdRO6bJ37pY7wuzzHKY-rgcN9lxY5IxurmSx44/edit

messages: https://www.figma.com/design/qxwVpxJJTpc8OsylbN7S95/Root-Certificate-Succession?node-id=7-860&t=LZg5Wf2V2mCEKwKO-0

Please include links to any design assets, visuals, figma files, etc. [REQUIRED]

Note: Ensure to submit only final visual assets relevant to the Production release, excluding Nightly or Beta images, and favor 'Light mode' UI screenshots over 'Dark mode'

TBD

Please add instructions for testing that will enable us to replicate the expected product behavior. [REQUIRED]

N/A

Does the content need approval before publishing? If yes, identify the one approver responsible for this task.

Yes - Venetia Tay & Jeff Pfaller

We want to make sure that it aligns with the message we are communicating to users. Jeff is working with legal on what wording we need to include etc.

Note: Minor changes such as string updates are directly handled in SUMO, and will not lead to the generation of a pre-publishing draft. [REQUIRED]

This is fixable if a user updates to Fx128 + ( or ESR 115.13+ for Windows 7/8/8.1 users).

btw, like Windows 7/8/8.1 users, macOS 10.12 - 10.14 users need to update ESR 115.13+. Fx 116+ dropped support for Windows < 10 and macOS < 10.15.

Assignee: nobody → lsiebert

We will also want to create SUMO threads that we can link to from the article, so users that have more questions can ask the support team. We'll want separate threads for desktop and Android users.

Kiki says the SUMO threads auto-lock after 180 days. We'll either want to keep unlocking these threads until the March 2025 expiration date or (if the threads get many replies) open new threads for each message.

Why cant users just be direceted to the Support Forum to ask a question? Threads tend to be a one user - one question approach with users getting emails on responses. As more people join the same question, the more people are being spammed by other peoples questions.

Hi Paul, you have a good point, there. However, we don't expect a lot of questions, so we think directing people to a single thread will make the tracking easier for us and help us to consolidate consistent messaging.

Will this still be a thread that contributors will be answering?

We've postponed our first message from September to October 9, a week after the Fx 131 release.

Will this still be a thread that contributors will be answering?

Yes. If using one thread proves too annoying or cumbersome, we can change our messaging to ask people to ask their questions in new threads.

I’ve incorporated the feedback from the Product team, and the content is now ready for a second review. https://docs.google.com/document/d/1sUbYfvF4bcgmwuWzXLAZDf0BUtQ0mgw04Ed44ZkwVjg/edit

Flags: needinfo?(vtay)

The KB article is now live: https://support.mozilla.org/en-US/kb/root-certificate-expiration. You can also find the Support Forum thread for this issue here: https://support.mozilla.org/en-US/questions/1468274.

Status: NEW → RESOLVED
Closed: 10 months ago
Flags: needinfo?(vtay)
Resolution: --- → FIXED
Depends on: 1953280
You need to log in before you can comment on or make changes to this bug.