• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..10-Feb-2022-

ref10/H10-Feb-2022-4,6863,453

READMEH A D10-Feb-20221.1 KiB2821

client_ed25519.cH A D10-Feb-20221.9 KiB6938

common.hH A D10-Feb-2022814 245

crypto_hash_sha512.hH A D10-Feb-2022106 32

crypto_int32.hH A D10-Feb-2022104 64

crypto_int64.hH A D10-Feb-2022104 64

crypto_sign.hH A D10-Feb-2022337 1413

crypto_uint32.hH A D10-Feb-2022106 64

crypto_uint64.hH A D10-Feb-2022106 64

crypto_verify.hH A D10-Feb-202266 21

crypto_verify_32.hH A D10-Feb-2022105 32

ed25519-t.cH A D10-Feb-20222 KiB5631

server_ed25519.cH A D10-Feb-20224 KiB14697

README

1This plugin uses public domain ed25519 code
2by Daniel J. Bernstein, Niels Duif, Tanja Lange, Peter Schwabe, Bo-Yin Yang.
3
4It is "ref10" implementation from the SUPERCOP:
5https://bench.cr.yp.to/supercop.html
6
7OpenSSH also uses ed25519 from SUPERCOP, but "ref" implementation.
8
9There are four ed25519 implementations in SUPERCOP, ref10 is faster then ref,
10and there are two that are even faster, written in amd64 assembler.
11Benchmarks are here: https://bench.cr.yp.to/impl-sign/ed25519.html
12
13==============================
14MariaDB changes:
15
16API functions were simplified to better fit our use case:
17* crypto_sign_open() does not return the verified message, only the
18  result of the verification (passed/failed)
19* no secret key is generated explicitly, user specified password is used
20  as a source of randomness instead (SHA512("user password")).
21* lengths are not returned, where they're known in advance
22  (e.g. from crypto_sign()).
23* crypto_sign() does not take the public key as an argument, but
24  generates it on the fly (we used to generate public key before
25  crypto_sign(), doing it internally avoids double work).
26
27See the changes done in this commit.
28