-
Notifications
You must be signed in to change notification settings - Fork 99
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
ecf93e9
commit be19cd9
Showing
1 changed file
with
10 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,10 @@ | ||
# Warning | ||
|
||
The SIDH and SIKE protocols were proven insecure after a series of attacks starting with [14]. | ||
Therefore, these protocols MUST NOT be used in production. | ||
|
||
The SIDH library is only presented here for historical reasons, and because some functionality may be reusable in other cryptographic applications. | ||
|
||
# SIDH v3.5.1 (C Edition) | ||
|
||
The **SIDH** library is an efficient supersingular isogeny-based cryptography library written in C language. | ||
|
@@ -263,6 +270,9 @@ The preprint version is available [`here`](https://eprint.iacr.org/2020/431). | |
[13] Patrick Longa, "Efficient algorithms for large prime characteristic fields and their application to bilinear pairings and supersingular isogeny-based protocols", 2022. | ||
The preprint version is available [`here`](https://eprint.iacr.org/2022/367). | ||
|
||
[14] Wouter Castryck and Thomas Decru, "An efficient key recovery attack on SIDH", 2022. | ||
The preprint version is available [`here`](https://eprint.iacr.org/2022/975). | ||
|
||
# Contributing | ||
|
||
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments. |