summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/curve25519/curve25519.h (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Expose direct access API for Ed25519.tb2022-11-131-3/+1
|
* zap stray space (CRITICAL!)tb2022-11-111-2/+2
|
* Rework ED25519 API.jsing2022-11-091-16/+12
| | | | | | | | | | | 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@
* Enable Ed25519 internal to libcrypto.jsing2022-11-061-1/+43
| | | | Based on a diff from tb@
* $OpenBSD$tb2019-05-111-0/+1
|
* Define X25519_KEY_LENGTH and use it so we have fewer magic numbers.jsing2016-12-171-3/+7
| | | | ok beck@
* Add support for X25519.jsing2016-11-051-0/+63
This brings in code from BoringSSL, which is mostly taken from SUPERCOP. ok beck@ bcook@