lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2593018.bJxuzB16oj@tauon.chronox.de>
Date:   Tue, 21 Jan 2020 12:40:21 +0100
From:   Stephan Mueller <smueller@...onox.de>
To:     Tianjia Zhang <tianjia.zhang@...ux.alibaba.com>
Cc:     herbert@...dor.apana.org.au, davem@...emloft.net,
        linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/6] lib/mpi: Introduce ec implementation to MPI library

Am Dienstag, 21. Januar 2020, 10:57:14 CET schrieb Tianjia Zhang:

Hi Tianjia,

> The implementation of EC is introduced from libgcrypt as the
> basic algorithm of elliptic curve, which can be more perfectly
> integrated with MPI implementation.
> Some other algorithms will be developed based on mpi ecc, such as SM2.

Why do we need a second implementation of ECC? Why can't we reuse the existing 
ECC implementation in crypto/ecc.c? Or are there limitations in the existing 
ECC implementation that cannot be fixed?

Thank you.

Ciao
Stephan


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ