Bug 615307

Summary: update webkitgtk to 1.2.3
Product: Red Hat Enterprise Linux 6 Reporter: Martin Stransky <stransky>
Component: webkitgtkAssignee: Martin Stransky <stransky>
Status: CLOSED CURRENTRELEASE QA Contact: desktop-bugs <desktop-bugs>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: syeghiay, tpelka, vdanen
Target Milestone: rcKeywords: Rebase, Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: webkitgtk-1.2.3-1.el6 Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-10 21:54:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Stransky 2010-07-16 13:32:43 UTC
Description of problem:

A new version has been released by upstream so we may rebase to it. See http://www.webkitgtk.org/?page=download

Comment 1 Vincent Danen 2010-07-16 16:27:26 UTC
From the NEWS file:

What's new in WebKitGTK+ 1.2.3?

  - New stable release, API and ABI compatible with previous 1.2.x
    versions;
  - Includes a fix to build WebKit with ICU 4.4.1
  - The patches to fix the following CVEs are included, thanks to the
    work done by Michael Gilbert <michael.s.gilbert> for the
    Debian security team:

      CVE-2010-1386 CVE-2010-1392 CVE-2010-1405 CVE-2010-1407
      CVE-2010-1416 CVE-2010-1417 CVE-2010-1665 CVE-2010-1418
      CVE-2010-1421 CVE-2010-1422 CVE-2010-1501 CVE-2010-1767
      CVE-2010-1664 CVE-2010-1758 CVE-2010-1759 CVE-2010-1760
      CVE-2010-1761 CVE-2010-1762 CVE-2010-1770 CVE-2010-1771
      CVE-2010-1772 CVE-2010-1773 CVE-2010-1774

We definitely want this in there.

Comment 3 releng-rhel@redhat.com 2010-11-10 21:54:54 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.