Changes between Version 10 and Version 11 of QtWebKitSecurity


Ignore:
Timestamp:
Sep 27, 2011 2:23:53 PM (13 years ago)
Author:
Ademar Reis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • QtWebKitSecurity

    v10 v11  
    33!QtWebKit follows WebKit's security policy, which is documented in http://www.webkit.org/security/
    44
    5 The !QtWebKit project makes only source-code releases and is not responsible for delivering binary packages to end users, which should get updates from their respective vendor (Linux distributions, device vendor, etc).
     5The !QtWebKit project makes only [wiki:QtWebKitReleases source-code releases] and is not responsible for delivering binary packages to end users, which should get updates from their respective vendor (Linux distributions, device vendor, etc).
    66
    7 !QtWebKit-2.2.0 is up-to-date regarding security vulnerabilities found in the WebKit codebase up to its release in September, 2011. Later updates on the 2.2 series will include security fixes and their announcements will be listed on this page.
     7[wiki:QtWebKitRelease22 QtWebKit-2.2.0] is up-to-date regarding security vulnerabilities found in the WebKit codebase up to its release in September, 2011. Later updates on the 2.2 series will include security fixes and their announcements will be listed on this page.
    88
    99== Security Announcements ==
    … …  
    3939== Preparing Security Announcements ==
    4040
    41 Part of the release-notes of patch-level releases (such as !QtWebKit-2.2.1, !QtWebKit-2.2.2, etc) should be dedicated to the security problems which have been fixed. It's standard procedure to include a list of security issues fixed (including the CVE Id) and give credit to the researchers who discovered and reported it.
     41Part of the release-notes of [wiki:QtWebKitReleases patch-level releases] (such as !QtWebKit-2.2.1, !QtWebKit-2.2.2, etc) should be dedicated to the security problems which have been fixed. It's standard procedure to include a list of issues (including the [http://cve.mitre.org/ CVE Id]) and give credit to the researchers who discovered and reported it.
    4242
    4343Examples of security announcements: