Hello community,

here is the log from the commit of package chromium for openSUSE:Factory 
checked in at 2015-02-16 21:47:01
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/chromium (Old)
 and      /work/SRC/openSUSE:Factory/.chromium.new (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "chromium"

Changes:
--------
--- /work/SRC/openSUSE:Factory/chromium/chromium.changes        2015-02-08 
13:04:14.000000000 +0100
+++ /work/SRC/openSUSE:Factory/.chromium.new/chromium.changes   2015-02-16 
21:47:10.000000000 +0100
@@ -1,0 +2,11 @@
+Sun Feb  8 21:13:30 UTC 2015 - [email protected]
+
+- Update to Chromium 40.0.2214.111
+  * Security Fixes:
+    - CVE-2015-1209: Use-after-free in DOM
+    - CVE-2015-1210: Cross-origin-bypass in V8 bindings
+    - CVE-2015-1211: Privilege escalation using service workers
+    - CVE-2015-1212: Various fixes from internal audits, fuzzing 
+                     and other initiatives
+
+-------------------------------------------------------------------

Old:
----
  chromium-40.0.2214.94.tar.xz

New:
----
  chromium-40.0.2214.111.tar.xz

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ chromium.spec ++++++
--- /var/tmp/diff_new_pack.p3TSyt/_old  2015-02-16 21:47:18.000000000 +0100
+++ /var/tmp/diff_new_pack.p3TSyt/_new  2015-02-16 21:47:18.000000000 +0100
@@ -20,7 +20,7 @@
 %define chromium_system_libs 0
 
 Name:           chromium
-Version:        40.0.2214.94
+Version:        40.0.2214.111
 Release:        0
 Summary:        Google's opens source browser project
 License:        BSD-3-Clause and LGPL-2.1+


++++++ chromium-40.0.2214.94.tar.xz -> chromium-40.0.2214.111.tar.xz ++++++
/work/SRC/openSUSE:Factory/chromium/chromium-40.0.2214.94.tar.xz 
/work/SRC/openSUSE:Factory/.chromium.new/chromium-40.0.2214.111.tar.xz differ: 
char 27, line 1


-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to