<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in vulnerability.rst</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>45c1608d - doc: clarify experimental API status in security process</title>
        <link>http://172.16.0.5:8080/history/dpdk/doc/guides/contributing/vulnerability.rst#45c1608d</link>
        <description>doc: clarify experimental API status in security processExplicitly note that experimental APIs also part of security process.Signed-off-by: Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;Acked-by: John McNamara &lt;john.mcnamara@intel.com&gt;

            List of files:
            /dpdk/doc/guides/contributing/vulnerability.rst</description>
        <pubDate>Mon, 17 Jun 2019 16:06:48 +0000</pubDate>
        <dc:creator>Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>4f041696 - doc: clarify security pre-release end of embargo date</title>
        <link>http://172.16.0.5:8080/history/dpdk/doc/guides/contributing/vulnerability.rst#4f041696</link>
        <description>doc: clarify security pre-release end of embargo dateClarify that a fixed date will be used for end of embargo (publicdisclosure) date while communicating with downstream stakeholders.Initial document got a review that it gives an impression thatcommunicated embargo date can be a range like &apos;less than a week&apos; whichis not the case. The range applies when defining the end of the embargodate but a fix date will be communicated.Signed-off-by: Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;Acked-by: John McNamara &lt;john.mcnamara@intel.com&gt;

            List of files:
            /dpdk/doc/guides/contributing/vulnerability.rst</description>
        <pubDate>Mon, 17 Jun 2019 16:06:47 +0000</pubDate>
        <dc:creator>Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>3d4b2afb - doc: prefer https when pointing to dpdk.org</title>
        <link>http://172.16.0.5:8080/history/dpdk/doc/guides/contributing/vulnerability.rst#3d4b2afb</link>
        <description>doc: prefer https when pointing to dpdk.orgfor file in $(git grep -l http://.*dpdk.org doc/); do  sed -i -e &apos;s#http://\(.*dpdk.org\)#https://\1#g&apos; $file;doneCc: stable@dpdk.orgSigned-off-by: David Marchand &lt;david.marchand@redhat.com&gt;Acked-by: Kevin Traynor &lt;ktraynor@redhat.com&gt;

            List of files:
            /dpdk/doc/guides/contributing/vulnerability.rst</description>
        <pubDate>Thu, 19 Mar 2020 08:28:59 +0000</pubDate>
        <dc:creator>David Marchand &lt;david.marchand@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>a46987cf - doc: add oss-security to the security process</title>
        <link>http://172.16.0.5:8080/history/dpdk/doc/guides/contributing/vulnerability.rst#a46987cf</link>
        <description>doc: add oss-security to the security processThe OSS-security project functions as a single point of contact forpre-release, embargoed security notifications. Distributions and majorvendors are subscribed to this private list, so that they can be warnedin advance and schedule the work required to fix the vulnerability.List and link this process in the DPDK security process document.Signed-off-by: Luca Boccassi &lt;luca.boccassi@microsoft.com&gt;Reviewed-by: Maxime Coquelin &lt;maxime.coquelin@redhat.com&gt;

            List of files:
            /dpdk/doc/guides/contributing/vulnerability.rst</description>
        <pubDate>Sat, 21 Sep 2019 14:52:42 +0000</pubDate>
        <dc:creator>Luca Boccassi &lt;luca.boccassi@microsoft.com&gt;</dc:creator>
    </item>
<item>
        <title>baf9fba3 - doc: prepare security process for vulnerabilities</title>
        <link>http://172.16.0.5:8080/history/dpdk/doc/guides/contributing/vulnerability.rst#baf9fba3</link>
        <description>doc: prepare security process for vulnerabilitiesIn case a vulnerability is discovered, the process to followis described in this document.It has been inspired by the process of some referenced projectsand with the help of experts from Intel, RedHat, Mellanoxand the Linux Foundation.Signed-off-by: Thomas Monjalon &lt;thomas@monjalon.net&gt;Signed-off-by: Maxime Coquelin &lt;maxime.coquelin@redhat.com&gt;Signed-off-by: Ferruh Yigit &lt;ferruh.yigit@intel.com&gt;Acked-by: Stephen Hemminger &lt;stephen@networkplumber.org&gt;Acked-by: Luca Boccassi &lt;bluca@debian.org&gt;

            List of files:
            /dpdk/doc/guides/contributing/vulnerability.rst</description>
        <pubDate>Tue, 07 May 2019 16:02:31 +0000</pubDate>
        <dc:creator>Thomas Monjalon &lt;thomas@monjalon.net&gt;</dc:creator>
    </item>
</channel>
</rss>
