Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Make X25519_public_from_private() internally reachable. | jsing | 2022-11-09 | 1 | -1/+4 |
| | |||||
* | Rework ED25519 API. | jsing | 2022-11-09 | 1 | -3/+3 |
| | | | | | | | | | | | BoringSSL implemented a compound private key, which includes a copy of the public key as a performance optimisation for signing. However, this does not readily match with how EVP works, makes the ED25519 API inconsistent with the X25519 API, diverges from th RFC and does not align with the OpenSSL API. Instead, the caller can readily compute the public key and pass this in to the signing process. ok tb@ | ||||
* | Refactor/split ED25519_keypair. | jsing | 2022-11-08 | 1 | -1/+4 |
| | | | | | | This brings in ED25519_keypair_from_seed() from BoringSSL commit c034e2d3ce16, which ED25519_keypair then wraps. This reduces differences between us and BoringSSL. | ||||
* | $OpenBSD$ | tb | 2019-05-11 | 1 | -0/+1 |
| | |||||
* | Use __{BEGIN,END}_HIDDEN_DECLS to avoid exporting the internal symbols | guenther | 2016-11-07 | 1 | -6/+2 |
| | | | | ok jsing@ | ||||
* | Add support for X25519. | jsing | 2016-11-05 | 1 | -0/+102 |
This brings in code from BoringSSL, which is mostly taken from SUPERCOP. ok beck@ bcook@ |