mariadb/plugin/auth_ed25519
Sergei Golubchik 6bf866cc79 MDEV-25641 max_password_errors not working with ed25519 auth plugin
report correct error codes in ed25519.
Invalid value stored in the user table or an OpenSSL error is CR_ERROR.
When a user provided incorrect password when logging in -
it's CR_AUTH_USER_CREDENTIALS.
2021-05-22 21:56:51 +02:00
..
ref10
client_ed25519.c Merge branch '5.5' into 10.1 2019-05-11 22:19:05 +03:00
CMakeLists.txt switch to CC 3.1 2019-07-20 09:09:28 +02:00
common.h Merge branch '5.5' into 10.1 2019-05-11 22:19:05 +03:00
crypto_hash_sha512.h
crypto_int32.h
crypto_int64.h
crypto_sign.h
crypto_uint32.h
crypto_uint64.h
crypto_verify.h
crypto_verify_32.h
ed25519-t.c
README
server_ed25519.c MDEV-25641 max_password_errors not working with ed25519 auth plugin 2021-05-22 21:56:51 +02:00

This plugin uses public domain ed25519 code
by Daniel J. Bernstein, Niels Duif, Tanja Lange, Peter Schwabe, Bo-Yin Yang.

It is "ref10" implementation from the SUPERCOP:
https://bench.cr.yp.to/supercop.html

OpenSSH also uses ed25519 from SUPERCOP, but "ref" implementation.

There are four ed25519 implementations in SUPERCOP, ref10 is faster then ref,
and there are two that are even faster, written in amd64 assembler.
Benchmarks are here: https://bench.cr.yp.to/impl-sign/ed25519.html

==============================
MariaDB changes:

API functions were simplified to better fit our use case:
* crypto_sign_open() does not return the verified message, only the
  result of the verification (passed/failed)
* no secret key is generated explicitly, user specified password is used
  as a source of randomness instead (SHA512("user password")).
* lengths are not returned, where they're known in advance
  (e.g. from crypto_sign()).
* crypto_sign() does not take the public key as an argument, but
  generates it on the fly (we used to generate public key before
  crypto_sign(), doing it internally avoids double work).

See the changes done in this commit.