<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="phui-timeline-shell"
      data-sigil="transaction anchor-container" data-meta="0_112">
      <div class="phui-timeline-event-view phui-timeline-major-event">
        <div class="phui-timeline-content">
          <div class="phui-timeline-group">
            <div class="phui-timeline-inner-content">
              <div class="phui-timeline-core-content"><span
                  class="transaction-comment"
                  data-sigil="transaction-comment" data-meta="0_62">
                  <div class="phabricator-remarkup">
                    <p>We delivered with some delay our completed
                      version of the integration of PQC algorithms into
                      Libgcrypt from our project in an <a
                        href="https://dev.gnupg.org/T6637#188370">upload
                        to this issue in phabricator</a>. The code
                      features the following algorithms:</p>
                    <div class="remarkup-code-block"
                      data-code-lang="text"
                      data-sigil="remarkup-code-block">
                      <pre class="remarkup-code">KMAC
ML-KEM
ML-DSA
SLH-DSA</pre>
                    </div>
                    <p>For each algorithm, also tests are implemented.
                      The patch is in the file
                      all-pqc-dfa4150a-vs-master-dc1c916d.patch. This is
                      a patch against the upstream master branch as
                      indicated by the commit version in the file name.
                      Rebasing our changes to current master was not
                      possible as since the start of our development
                      work, ML-KEM was introduced into Libgcrypt
                      independently by the maintainers and thus an
                      attempt to merge both branches would either
                      feature two versions of the same algorithm or
                      would have to remove one of them. Even though we
                      do not expect that our ML-KEM implementation will
                      still be used by the Libgcrypt project, we decided
                      to provide the patch with our complete
                      contribution. We would appreciate if the
                      maintainers would follow up with comments as to in
                      which form our patch is the most useful to them.
                      Particularly, we are contributing PQC signature
                      algorithms which to the best of our knowledge have
                      so far not been in implemented in Libgcrypt and
                      thus might be of interest to the project. If the
                      maintainers prefer that these algorithms be
                      submitted in a different form, please let us know
                      and we will try to find the best possible solution
                      so that the Libgcrypt project can benefit from our
                      contribution.</p>
                  </div>
                </span></div>
            </div>
          </div>
        </div>
      </div>
    </div>
    <div class="phui-timeline-event-view phui-timeline-spacer"><span
        class="transaction-comment" data-sigil="transaction-comment"
        data-meta="0_62">Note: my DCO form Sept. '23 applies to this
        patch.</span></div>
    <div class="phui-timeline-event-view phui-timeline-spacer">Signed-off-by:
      Falko Strenzke <a class="moz-txt-link-rfc2396E"
        href="mailto:falko.strenzke@mtg.de"><falko.strenzke@mtg.de></a></div>
    <div class="phui-timeline-event-view phui-timeline-spacer"><span
        class="transaction-comment" data-sigil="transaction-comment"
        data-meta="0_62"><br>
      </span></div>
    <p></p>
    <div class="moz-signature">-- <br>
      <!-- MTG AG HTML signature v.1.0, 2021-02-12 - Author: Andreas Cholet -->
      <div style="font-family: Arial,serif">
        <p
style="line-height: 1.5; font-size: small; color: rgb(93, 93, 95);"> <strong>MTG
            AG</strong><br>
          Dr. Falko Strenzke <br>
        </p>
        <p style="font-size: small; color: rgb(93, 93, 95);"> <span
            style="display:inline-block;width:4em">Phone: </span>+49
          6151 8000 24<br>
          <span style="display:inline-block;width:4em">E-Mail: </span><a class="moz-txt-link-abbreviated" href="mailto:falko.strenzke@mtg.de">falko.strenzke@mtg.de</a><br>
          <span style="display:inline-block;width:4em">Web: </span><a
            href="https://www.mtg.de" title="MTG AG Internet"
            target="_blank">mtg.de</a>
        </p>
        <hr
style="width:250px; text-align:left;margin-left:0; height: 0,1">
        <table>
          <tbody>
            <tr>
              <td><br>
              </td>
              <td><br>
              </td>
            </tr>
          </tbody>
        </table>
        <p
style="line-height: 1.2; font-size: x-small; color: rgb(93, 93, 95);">
          MTG AG - Dolivostr. 11 - 64293 Darmstadt, Germany<br>
          Commercial register: HRB 8901<br>
          Register Court: Amtsgericht Darmstadt<br>
          Management Board: Jürgen Ruf (CEO), Tamer Kemeröz<br>
          Chairman of the Supervisory Board: Dr. Thomas Milde<br>
          <br>
          This email may contain confidential and/or privileged
          information. If you are not the correct recipient or have
          received this email in error, <br>
          please inform the sender immediately and delete this
          email.Unauthorised copying or distribution of this email is
          not permitted.<br>
          <br>
          Data protection information: <a
            href="https://www.mtg.de/en/privacy-policy"
            title="MTG Privacy policy" target="_blank">Privacy policy</a>
        </p>
      </div>
    </div>
  </body>
</html>