Skip to content

O
openssl

btwise / openssl

通知 1
Star 0
Fork 0
O
openssl

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 12 12月, 2019 1 次提交
  3. 09 12月, 2019 1 次提交
  5. 06 12月, 2019 1 次提交
  7. 04 12月, 2019 1 次提交
  9. 30 11月, 2019 5 次提交
    • R
      PROV SERIALIZER: add support for writing RSA keys · 677add38
      由 Richard Levitte 提交于 
      This also adds the missing accessor RSA_get0_pss_params(), so those
parameters can be included in the PKCS#8 data structure without
needing to know the inside of the RSA structure.
Reviewed-by: NMatt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10394)
      677add38
    • R
      PROV SERIALIZER: add common functionality to serialize keys · cb58d81e
      由 Richard Levitte 提交于 
      To support generic output of public keys wrapped in a X509_PUBKEY,
additional PEM and i2d/d2i routines are added for that type.
Reviewed-by: NMatt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10394)
      cb58d81e
    • R
      SERIALIZER: add support for serializing EVP_PKEYs · 866234ac
      由 Richard Levitte 提交于 
      The following public functions is added:

- OSSL_SERIALIZER_CTX_new_by_EVP_PKEY()
- OSSL_SERIALIZER_CTX_set_cipher()
- OSSL_SERIALIZER_CTX_set_passphrase()
- OSSL_SERIALIZER_CTX_set_passphrase_cb()
- OSSL_SERIALIZER_CTX_set_passphrase_ui()

OSSL_SERIALIZER_CTX_new_by_EVP_PKEY() selects a suitable serializer
for the given EVP_PKEY, and sets up the OSSL_SERIALIZER_CTX to
function together with OSSL_SERIALIZER_to_bio() and
OSSL_SERIALIZER_to_fp().

OSSL_SERIALIZER_CTX_set_cipher() indicates what cipher should be used
to produce an encrypted serialization of the EVP_PKEY.  This is passed
directly to the provider using OSSL_SERIALIZER_CTX_set_params().

OSSL_SERIALIZER_CTX_set_passphrase() can be used to set a pass phrase
to be used for the encryption.  This is passed directly to the
provider using OSSL_SERIALIZER_CTX_set_params().

OSSL_SERIALIZER_CTX_set_passphrase_cb() and
OSSL_SERIALIZER_CTX_set_passphrase_ui() sets up a callback to be used
to prompt for a passphrase.  This is stored in the context, and is
called via an internal intermediary at the time of serialization.
Reviewed-by: NMatt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10394)
      866234ac
    • R
      SERIALIZER: add functions for serialization to file · 742496f1
      由 Richard Levitte 提交于 
      These functions are added:

- OSSL_SERIALIZER_to_bio()
- OSSL_SERIALIZER_to_fp() (unless 'no-stdio')

OSSL_SERIALIZER_to_bio() and OSSL_SERIALIZER_to_fp() work as wrapper
functions, and call an internal "do_output" function with the given
serializer context and a BIO to output the serialized result to.

The internal "do_output" function must have intimate knowledge of the
object being output.  This will defined independently with context
creators for specific OpenSSL types.
Reviewed-by: NMatt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10394)
      742496f1
    • R
      SERIALIZER: New API for serialization of objects through providers · 0d003c52
      由 Richard Levitte 提交于 
      Serialization is needed to be able to take a provider object (such as
the provider side key data) and output it in PEM form, DER form, text
form (for display), and possibly other future forms (XML? JSON? JWK?)

The idea is that a serializer should be able to handle objects it has
intimate knowledge of, as well as object data in OSSL_PARAM form.  The
latter will allow libcrypto to serialize some object with a different
provider than the one holding the data, if exporting of that data is
allowed and there is a serializer that can handle it.

We will provide serializers for the types of objects we know about,
which should be useful together with any other provider that provides
implementations of the same type of object.

Serializers are selected by method name and a couple of additional
properties:

- format        used to tell what format the output should be in.
                Possibilities could include "format=text",
                "format=pem", "format=der", "format=pem-pkcs1"
                (traditional), "format=der-pkcs1" (traditional)
- type          used to tell exactly what type of data should be
                output, for example "type=public" (the public part of
                a key), "type=private" (the private part of a key),
                "type=domainparams" (domain parameters).

This also adds a passphrase callback function type,
OSSL_PASSPHRASE_CALLBACK, which is a bit like OSSL_CALLBACK, but it
takes a few extra arguments to place the result in.
Reviewed-by: NMatt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/10394)
      0d003c52
  11. 28 11月, 2019 3 次提交
  13. 17 11月, 2019 1 次提交
  15. 16 11月, 2019 1 次提交
  17. 14 11月, 2019 3 次提交
  19. 13 11月, 2019 2 次提交
  21. 12 11月, 2019 1 次提交
  23. 11 11月, 2019 1 次提交
  25. 08 11月, 2019 1 次提交
  27. 07 11月, 2019 3 次提交
  29. 06 11月, 2019 2 次提交
  31. 04 11月, 2019 3 次提交
  33. 03 11月, 2019 1 次提交
  35. 31 10月, 2019 2 次提交
  37. 29 10月, 2019 1 次提交
  39. 28 10月, 2019 2 次提交
  41. 24 10月, 2019 1 次提交
  43. 23 10月, 2019 3 次提交