Whatś the Mint take on the FF16 security vulnerability

[seba]

L.S./Hi guys

Just read about the reported (minor) Firefox 16 security vulnerability https://blog.mozilla.org/security/2012/10/10/security-vulnerability-in-firefox-16/.
Will you guys keep (offering) FFv16 in the (buntu) repo? I see it's still being offered when I updated Maya.

[karlchen]

Hello, seba.

Hm, just a few minutes ago I have received Firefox 16.0.1.

Code: Select all

firefox (16.0.1+build1-0ubuntu0.12.04.1) precise-security; urgency=low
  * New upstream stable release (FIREFOX_16_0_1_BUILD1)
    - see LP: #1065285 for USN information
 -- Chris Coulson <chris.coulson@canonical.com>  Wed, 10 Oct 2012 23:28:46 +0100

I do hope this is the fixed version....

<added a few minutes later coming back from Launchpad>
Telling from the Launchpad comment here, this is the bug-fixed release.
</added a few minutes later coming back from Launchpad>

Karl

[lexon]

I just reed about this issue and wondering also.

Edit.

The previous message seems to say this is fixed.

L

[martywd]

...
Hm, just a few minutes ago I have received Firefox 16.0.1.
[code]firefox (16.0.1+build1-0ubuntu0.12.04.1) precise-security; urgency=low

Thanks for the head up. This does looks like the release fix for the issue with FF 16?

==> https://bugs.launchpad.net/ubuntu/+sour ... ug/1065285
.

[karlchen]

Hi, martywd.

Telling from the original bug description, yes, F.F. 16.0.1 fixes the bug(s). And the official repositories by now offer F.F. 16.0.1.
I.e. F.F. 16.0 holds the bugs, but provided your Firefox confirms it is version 16.0.1 then you are using the fixed version.

Karl

[martywd]

Hi, martywd.

Telling from the original bug description, yes, F.F. 16.0.1 fixes the bug(s). And the official repositories by now offer F.F. 16.0.1.
I.e. F.F. 16.0 holds the bugs, but provided your Firefox confirms it is version 16.0.1 then you are using the fixed version.

Karl

Yes. Understood. Thanks.

FWIW, Ubuntu has served notice as well: ==> http://www.ubuntu.com/usn/usn-1608-1/
.

[seba]

Great, fixed already so afaic this thread can be closed/marked as solved.