<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><font size="+1">Hi Jason,</font><br>
    </p>
    <div class="moz-signature">Ondrej Zizka, Red Hat Migration Toolkit</div>
    <div class="moz-cite-prefix">On 12.6.2017 01:30, Jason Shepherd
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CA+Bbw+bLi6aZvFnSG-vke-GQRD_EBhnxSuMT9q0yABwPEtf1+w@mail.gmail.com">
      <div dir="ltr">Hi Ondrej,
        <div><br>
        </div>
        <div>Sorry for the late reply on this. Stephen and I have been
          discussing the Victims project lately and I realised I hadn't
          forwarded his feedback to him, so please see his replies to
          your feedback below.</div>
        <div><br>
        </div>
        <div>However I think we are going to refocus our efforts a bit
          on Victims. OWASP dependency check has become a very popular
          project for vulnerability tracking. It's being used by Fabric8
          for vulnerability scanning in Openshift.IO at the moment. The
          OWASP project is willing to add Victims as a datasource, so I
          think we should focus our efforts on that in order to get
          their features, and also have some influence on the data in
          that tool.</div>
      </div>
    </blockquote>
    Good news!<br>
    <blockquote type="cite"
cite="mid:CA+Bbw+bLi6aZvFnSG-vke-GQRD_EBhnxSuMT9q0yABwPEtf1+w@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>One thing that the community are asking for is a change in
          licence for the victims-cve-db part of the project, so that's
          something that we'll definitely we looking at. Some members
          have suggested a CC BY-SA licence. What do you think of that?
          Read the discussion here:</div>
        <div><br>
        </div>
        <div> <a
            href="https://github.com/victims/victims-cve-db/issues/25"
            moz-do-not-send="true">https://github.com/victims/victims-cve-db/issues/25</a></div>
      </div>
    </blockquote>
    I don't know much about licenses, maybe Marek will be able to tell
    more. I remember Windup would have a problem with the Java client
    lib being licensed under AGPL. Eclipse license would fit.<br>
    Regarding the db part and CC BY-SA, I guess someone (Tobias?) would
    have to consider.<br>
    <br>
    Ondra<br>
    <blockquote type="cite"
cite="mid:CA+Bbw+bLi6aZvFnSG-vke-GQRD_EBhnxSuMT9q0yABwPEtf1+w@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>Regards,</div>
        <div>Jason Shepherd</div>
        <div>Product Security</div>
        <div><br>
        </div>
        <div>
          <div class="gmail_quote">---------- Forwarded message
            ----------<br>
            From: <b class="gmail_sendername">Stephen Milner</b> <span
              dir="ltr">&lt;<a href="mailto:smilner@redhat.com"
                moz-do-not-send="true">smilner@redhat.com</a>&gt;</span><br>
            Date: Sat, Jun 10, 2017 at 4:45 AM<br>
            Subject: Re: Victims Java API, data, features<br>
            To: Jason Shepherd &lt;<a href="mailto:jshepher@redhat.com"
              moz-do-not-send="true">jshepher@redhat.com</a>&gt;<br>
            <br>
            <br>
            Replying back to you with details. In the response please do
            loop my address :-)<br>
            <br>
            Inline ...<br>
            <span class="gmail-"><br>
              On Fri, Jun 9, 2017 at 2:04 AM, Jason Shepherd &lt;<a
                href="mailto:jshepher@redhat.com" moz-do-not-send="true">jshepher@redhat.com</a>&gt;
              wrote:<br>
              &gt;<br>
              &gt; ---------- Forwarded message ----------<br>
              &gt; From: Ondrej Zizka &lt;<a
                href="mailto:ozizka@redhat.com" moz-do-not-send="true">ozizka@redhat.com</a>&gt;<br>
              &gt; Date: Wed, Jun 1, 2016 at 3:09 AM<br>
              &gt; Subject: Victims Java API, data, features<br>
              &gt; To: Jason Shepherd &lt;<a
                href="mailto:jshepher@redhat.com" moz-do-not-send="true">jshepher@redhat.com</a>&gt;,
              Windup-dev List<br>
              &gt; &lt;<a href="mailto:windup-dev@lists.jboss.org"
                moz-do-not-send="true">windup-dev@lists.jboss.org</a>&gt;<br>
              &gt;<br>
              &gt;<br>
              &gt;<br>
              &gt;<br>
              &gt;<br>
              &gt; Hi Jason,<br>
              &gt;<br>
              &gt; (I'm seding 2nd mail to start a new thread, please
              ignore the previous one.)<br>
              &gt;<br>
              &gt; I have looked closer at Víctims.<br>
              &gt; I have few questions/issues. Could you please help
              resolving those?<br>
              &gt;<br>
              &gt; Note: I'm adding a PUBLIC mailing list, Windup
              developers. Feel free to add<br>
              &gt; some Victims list (is there one?)<br>
              &gt;<br>
              &gt; 1) Hashes are not real checksums<br>
              &gt; As someone wrote in <a
                href="https://github.com/victims/victims-cve-db/issues/45"
                rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/victims/<wbr>victims-cve-db/issues/45</a><br>
              &gt; the hashes used by Victims are not just SHA512 hashes
              of the file content,<br>
              &gt; but something else.<br>
              &gt; I'd like to be able to either find CVE's by a normal
              file content hash, or<br>
              &gt; create the Victims hash.<br>
              <br>
            </span>That's a fair request. For some background, the
            reason we recreate a<br>
            specific hash<br>
            is that different Java implementations create different
            bytecode,<br>
            resulting in different<br>
            hashes. Our hash creator strips out implementation specific
            items for creating<br>
            and scanning.<br>
            <span class="gmail-"><br>
              &gt; a) Is there a Java impl?<br>
              <br>
            </span>Client side there is via <a
              href="https://github.com/victims/victims-lib-java"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/victims/<wbr>victims-lib-java</a><br>
            <span class="gmail-"><br>
              &gt; b) Could you add the plain SHA512 (or other, I'm okay
              with just CRC32) hash<br>
              &gt; to the data?<br>
              <br>
            </span>We could do so. I assume this would be the SHA512 of
            the vulnerable jar file.<br>
            <span class="gmail-"><br>
              &gt; 2) Victims Java client API<br>
              &gt;<br>
              &gt; The Java API doesn't match the needs much.<br>
              &gt;  From what I can see, it can<br>
              &gt;    a) Sync with the server<br>
              &gt;    b) Give me a list of CVE for given SHA512 hash.<br>
              &gt;<br>
              &gt; What I would like to have is:<br>
              &gt; * Have some offline data distributed with our app,
              provide these data<br>
              &gt; * Search the database by Maven coordinates, classes,<br>
              &gt; * Get a short description of the CVE and date of
              appearance and how/where it<br>
              &gt; was fixed<br>
              &gt;<br>
              &gt; Is there a plan for extending the Java API?<br>
              &gt; Also I guess not all these are covered in the Victims
              database, right?<br>
              <br>
            </span>You're correct. There is a disconnect between the
            victims-cve-db and the hash<br>
            database. Folks have been pretty great at submitting items
            to the victims-cve-db<br>
            but we've gotten very little submissions for the hash db.
            Part of me wonders<br>
            if it would be more beneficial to combine the two in the
            victims-cve-db. Syncing<br>
            would then be a ``git pull`` rather than API call. It would
            also let<br>
            people do PR's<br>
            for data inclusion which may be more submitter friendly.
            Thoughts?<br>
            <span class="gmail-"><br>
              &gt; 3) Configuration<br>
              &gt; The configuration is done through system properties,
              that's not too<br>
              &gt; fortunate.<br>
              &gt; For instance it doesn't allow to run multiple clients
              at once in the same<br>
              &gt; JVM.<br>
              &gt; Could that be done through an API?<br>
              <br>
            </span>I don't see why not. However, I think we would need
            some help to do that.<br>
            <span class="gmail-"><br>
              &gt; 4) Data structure<br>
              &gt; The data structure of the JSON is not obvious. Is
              there some docs for it?<br>
              <br>
            </span>No, but there should be. Here is some pointers I
            threw together:<br>
            <br>
            <a
              href="https://gist.github.com/ashcrow/df238b1cc1e8a2f4bba94a6bb310805e"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://gist.github.com/<wbr>ashcrow/<wbr>df238b1cc1e8a2f4bba94a6bb31080<wbr>5e</a><br>
            <span class="gmail-"><br>
              &gt; 5) Data storage<br>
              &gt; The data are only stored in a database over JDBC.
              Could it be simply stored<br>
              &gt; in a JSON or XML file? The file is just 165 KB and
              not growing too fast, so<br>
              &gt; I think rather than bringing an embedded DB as a
              dependency, I'd prefer to<br>
              &gt; process a XML file into a HashMap or a Lucene index
              and use that.<br>
              <br>
            </span>I added a possible replacement at<br>
            <a
              href="https://gist.github.com/ashcrow/df238b1cc1e8a2f4bba94a6bb310805e"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://gist.github.com/<wbr>ashcrow/<wbr>df238b1cc1e8a2f4bba94a6bb31080<wbr>5e</a>.<br>
            Essentially we'd move to a yaml format which is a combined
            version of<br>
            the victims-cve-db and the hash<br>
            database (which currently sits behind the api). Instead of
            syncing<br>
            with the API one would sync via git<br>
            and pull down the latest changes. PTAL and let me know what
            you think.<br>
            <div class="gmail-HOEnZb">
              <div class="gmail-h5"><br>
                <br>
                &gt; On 4.4.2016 02:16, Jason Shepherd wrote:<br>
                &gt;&gt;<br>
                &gt;&gt; Hi Ondra,<br>
                &gt;&gt;<br>
                &gt;&gt; The architecture of Victims is such that you
                should never need to<br>
                &gt;&gt; 'download' the database. The client is designed
                to connect to the<br>
                &gt;&gt; central <a href="http://victi.ms"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">http://victi.ms</a> API to get
                the latest vulnerabilities.<br>
                &gt;&gt;<br>
                &gt;&gt; That being said, the authors also have a
                'backup' of the data in the<br>
                &gt;&gt; form of a Github repository, [1]. In fact some
                members of the<br>
                &gt;&gt; community have built a tool which just uses
                this repository, and does<br>
                &gt;&gt; not use the API at all. Recently we've built a
                tool to rebuild the<br>
                &gt;&gt; database from the Github repository, but it
                still needs some work,<br>
                &gt;&gt; [3].<br>
                &gt;&gt;<br>
                &gt;&gt;     [1] <a
                  href="https://github.com/victims/victims-cve-db"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://github.com/victims/<wbr>victims-cve-db</a><br>
                &gt;&gt;     [2] <a
                  href="https://github.com/h3xstream/maven-security-versions"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://github.com/h3xstream/<wbr>maven-security-versions</a><br>
                &gt;&gt;     [3] <a
                  href="https://github.com/jasinner/victims-db-builder"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">https://github.com/jasinner/<wbr>victims-db-builder</a><br>
                &gt;&gt;<br>
                &gt;&gt; Let me know if you need any further
                information.<br>
                &gt;&gt; Regards,<br>
                &gt;&gt; Jason Shepherd<br>
                &gt;&gt;<br>
                &gt;&gt; On Fri, Apr 1, 2016 at 1:38 AM, Ondrej Zizka
                &lt;<a href="mailto:ozizka@redhat.com"
                  moz-do-not-send="true">ozizka@redhat.com</a>&gt;
                wrote:<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;&gt; Great to know it goes on, last time I
                talked to someone (I think djorm),<br>
                &gt;&gt;&gt; he<br>
                &gt;&gt;&gt; said the development was stagnant.<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;&gt; Jason, is there a way to download a single
                big file with all data in the<br>
                &gt;&gt;&gt; database?<br>
                &gt;&gt;&gt;<br>
                &gt;&gt;&gt; Thanks,<br>
                &gt;&gt;&gt; Ondra<br>
                &gt;<br>
                &gt;<br>
                <br>
                <br>
                <br>
              </div>
            </div>
            <span class="gmail-HOEnZb"><font color="#888888">--<br>
                Thanks,<br>
                Steve Milner<br>
                <br>
                Atomic | Red Hat | <a href="http://projectatomic.io/"
                  rel="noreferrer" target="_blank"
                  moz-do-not-send="true">http://projectatomic.io/</a> |
                <a href="http://commissaire.io" rel="noreferrer"
                  target="_blank" moz-do-not-send="true">http://commissaire.io</a><br>
              </font></span></div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>