EVP_SIGNATURE-ED25519.pod 3.0 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889
  1. =pod
  2. =head1 NAME
  3. EVP_SIGNATURE-ED25519,
  4. EVP_SIGNATURE-ED448,
  5. Ed25519,
  6. Ed448
  7. - EVP_PKEY Ed25519 and Ed448 support
  8. =head1 DESCRIPTION
  9. The B<Ed25519> and B<Ed448> EVP_PKEY implementation supports key generation,
  10. one-shot digest sign and digest verify using PureEdDSA and B<Ed25519> or B<Ed448>
  11. (see RFC8032). It has associated private and public key formats compatible with
  12. RFC 8410.
  13. No additional parameters can be set during one-shot signing or verification.
  14. In particular, because PureEdDSA is used, a digest must B<NOT> be specified when
  15. signing or verifying.
  16. See L<EVP_PKEY-X25519(7)> for information related to B<X25519> and B<X448> keys.
  17. =head1 NOTES
  18. The PureEdDSA algorithm does not support the streaming mechanism
  19. of other signature algorithms using, for example, EVP_DigestUpdate().
  20. The message to sign or verify must be passed using the one-shot
  21. EVP_DigestSign() and EVP_DigestVerify() functions.
  22. When calling EVP_DigestSignInit() or EVP_DigestVerifyInit(), the
  23. digest I<type> parameter B<MUST> be set to NULL.
  24. Applications wishing to sign certificates (or other structures such as
  25. CRLs or certificate requests) using Ed25519 or Ed448 can either use X509_sign()
  26. or X509_sign_ctx() in the usual way.
  27. Ed25519 or Ed448 private keys can be set directly using
  28. L<EVP_PKEY_new_raw_private_key(3)> or loaded from a PKCS#8 private key file
  29. using L<PEM_read_bio_PrivateKey(3)> (or similar function). Completely new keys
  30. can also be generated (see the example below). Setting a private key also sets
  31. the associated public key.
  32. Ed25519 or Ed448 public keys can be set directly using
  33. L<EVP_PKEY_new_raw_public_key(3)> or loaded from a SubjectPublicKeyInfo
  34. structure in a PEM file using L<PEM_read_bio_PUBKEY(3)> (or similar function).
  35. Ed25519 and Ed448 can be tested with the L<openssl-speed(1)> application
  36. since version 1.1.1.
  37. Valid algorithm names are B<ed25519>, B<ed448> and B<eddsa>. If B<eddsa> is
  38. specified, then both Ed25519 and Ed448 are benchmarked.
  39. =head1 EXAMPLES
  40. To sign a message using a ED25519 or ED448 key:
  41. void do_sign(EVP_PKEY *ed_key, unsigned char *msg, size_t msg_len)
  42. {
  43. size_t sig_len;
  44. unsigned char *sig = NULL;
  45. EVP_MD_CTX *md_ctx = EVP_MD_CTX_new();
  46. EVP_DigestSignInit(md_ctx, NULL, NULL, NULL, ed_key);
  47. /* Calculate the requires size for the signature by passing a NULL buffer */
  48. EVP_DigestSign(md_ctx, NULL, &sig_len, msg, msg_len);
  49. sig = OPENSSL_zalloc(sig_len);
  50. EVP_DigestSign(md_ctx, sig, &sig_len, msg, msg_len);
  51. ...
  52. OPENSSL_free(sig);
  53. EVP_MD_CTX_free(md_ctx);
  54. }
  55. =head1 SEE ALSO
  56. L<EVP_PKEY-X25519(7)>
  57. L<provider-signature(7)>,
  58. L<EVP_DigestSignInit(3)>,
  59. L<EVP_DigestVerifyInit(3)>,
  60. =head1 COPYRIGHT
  61. Copyright 2017-2020 The OpenSSL Project Authors. All Rights Reserved.
  62. Licensed under the Apache License 2.0 (the "License"). You may not use
  63. this file except in compliance with the License. You can obtain a copy
  64. in the file LICENSE in the source distribution or at
  65. L<https://www.openssl.org/source/license.html>.
  66. =cut