Opera 12.16 has been pushed to mga2+mga3 nonfree/updates_testing. This addresses at least this upstream advisory: http://www.opera.com/security/advisory/1048 I'll add a comment with the suggested update advisory as soon as the full changelog becomes available. Packages: opera-12.16-1.mga2.nonfree opera-12.16-1.mga3.nonfree
CC: (none) => davidwhodginsWhiteboard: (none) => MGA2TOO
http://svnweb.mageia.org/advisories/10693.adv?sortby=date&view=log uploaded. Testing complete on Mageia 2 and 3, i586 and x86_64. Anssi, Should I go ahead and validate this update, or wait till the advisory can be updated?
Whiteboard: MGA2TOO => MGA2TOO MGA3-64-OK MGA3-32-OK MGA2-64-OK MGA2-32-OK
Let's wait a bit more (max 10 hours).
Suggested advisory: ======================= description: | Opera 12.16 contains a replaced code signing certificate. Opera Software recently experienced an attack on the internal infrastructure. Following best practices, Opera Software is replacing signing certificates in Opera with newly issued certificates. Certificates in Opera include the code signing certificate for desktop binaries and the signing certificate for automatic updates to browser.js. Opera's rootstore was not affected by the attack and certificates used for accessing HTTPS websites are unchanged by this update. references: - https://bugs.mageia.org/show_bug.cgi?id=10693 - http://www.opera.com/docs/changelogs/unified/1216/ - http://www.opera.com/security/advisory/1048 ======================= OK to validate.
Thanks Anssi. Validating. Advisory updated. Could sysadmin please push from 2 & 3 nonfree/updates_testing to nonfree/updates Thanks!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
http://advisories.mageia.org/MGASA-2013-0202.html
Status: ASSIGNED => RESOLVEDCC: (none) => boklmResolution: (none) => FIXED
CC: boklm => (none)