History log of /openbsd-src/lib/libcrypto/curve25519/curve25519.h (Results 1 – 7 of 7)
Revision Date Author Comments
# d6a7ea16 13-Nov-2022 tb <tb@openbsd.org>

Expose direct access API for Ed25519.


# ba2d5144 11-Nov-2022 tb <tb@openbsd.org>

zap stray space (CRITICAL!)


# 5b0711d2 09-Nov-2022 jsing <jsing@openbsd.org>

Rework ED25519 API.

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

Rework ED25519 API.

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@

show more ...


# adc9c116 06-Nov-2022 jsing <jsing@openbsd.org>

Enable Ed25519 internal to libcrypto.

Based on a diff from tb@


# 694cb796 11-May-2019 tb <tb@openbsd.org>

$OpenBSD$


# a878ae04 17-Dec-2016 jsing <jsing@openbsd.org>

Define X25519_KEY_LENGTH and use it so we have fewer magic numbers.

ok beck@


# 5f5d09a5 05-Nov-2016 jsing <jsing@openbsd.org>

Add support for X25519.

This brings in code from BoringSSL, which is mostly taken from SUPERCOP.

ok beck@ bcook@