Changes between Version 6 and Version 7 of QtWebKitSecurity


Ignore:
Timestamp:
Sep 27, 2011, 1:35:27 PM (13 years ago)
Author:
Ademar Reis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • QtWebKitSecurity

    v6 v7  
    99== Security Announcements ==
    1010
    11 Security reports are sent to the [http://lists.qt.nokia.com/mailman/listinfo/qtwebkit-announce QtWebKit Announcements mailing list]
     11Security reports are sent to the [http://lists.qt.nokia.com/mailman/listinfo/qtwebkit-announce QtWebKit Announcements mailing list]. Below is a list of announcements made so far:
    1212
    1313  * None yet (this will be a list of links to the announcements mailing list)
    … …  
    2121   * [http://support.apple.com/kb/HT4808 Apple Safari]
    2222
    23 The list of security bugs fixed in the branch since the last release can be extracted from the git changelog using the {{{cherry-pick-into-release-branch.py}}} script. For example, to extract a list of all security issues fixed from the tag {{{qtwebkit-2.2.0}}} until now:
    24 (notice you'll need proper bugzilla privileges)
     23The list of security bugs fixed in the branch since the last release can be extracted from the git changelog using the {{{cherry-pick-into-release-branch.py}}} script. For example, to extract a list of all security issues fixed from the tag {{{qtwebkit-2.2.0}}} until now (notice you'll need proper bugzilla privileges):
    2524
    2625{{{
    … …  
    3029With this list in hand, we can go to Bugzilla and find out, manually:
    3130  * The CVE Id of the issue;
    32   * The researchers who should receive credit;
     31  * The researchers who should receive credit.
    3332
    34 Once the release notes is ready, it should be sent to the [mailto:security@webkit.org WebKit Security mailing list] for peer review. Preferably one or two days before making it public. Exceptions and any topic regarding the security policy can be also discussed there.
     33Once the release notes is ready, it should be sent to the [mailto:security@webkit.org WebKit Security mailing list] for peer review. Preferably one or two days before making it public. Exceptions and any topics regarding the security policy can be also discussed there.