FEDORA-2024-f109ae6fc7 — security update for firefox

stable

firefox-131.0.2-1.fc39

FEDORA-2024-f109ae6fc7 created by stransky a year ago for Fedora 39

Updated to latest upstream (131.0.2)

Logout Required

After installing this update it is required that you logout of your current user session and log back in to ensure the changes supplied by this update are applied properly.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2024-f109ae6fc7

This update has been submitted for testing by stransky.

a year ago

This update's test gating status has been changed to 'waiting'.

a year ago

This update's test gating status has been changed to 'passed'.

a year ago

This update has been pushed to testing.

a year ago

mschwarz commented & provided feedback a year ago

karma

works for me

Test Case firefox addons

Test Case firefox browse

Test Case firefox media

nucleo commented a year ago

SEC_ERROR_REVOKED_CERTIFICATE on https://dl.fedoraproject.org/ (opens fine in chromium)

mrc0mmand commented & provided feedback a year ago

karma

Seems to work as expected, but I came across the same issue @nucleo already mentioned - https://dl.fedoraproject.org/ now returns:


Secure Connection Failed

An error occurred during a connection to dl.fedoraproject.org. Peer’s Certificate has been revoked.

Error code: SEC_ERROR_REVOKED_CERTIFICATE

But it worked fine with firefox-130.0-3.fc39.x86_64.

Test Case firefox addons

Test Case firefox browse

Test Case firefox media

Test Case firefox screenshot

This update can be pushed to stable now if the maintainer wishes

a year ago

geraldosimiao provided feedback a year ago

karma

This update has been submitted for stable by bodhi.

a year ago

geraldosimiao commented a year ago

Yeah, overall working fine, but when we try to access https://dl.fedoraproject.org/pub/fedora/linux/development/41/ we have this error message: SEC_ERROR_REVOKED_CERTIFICATE

kevin commented a year ago

This is super unlikely to have anything to do with this firefox update. It should be fixed now, if not please file a infrastructure ticket and we can track it down.