Dmitry Belyavskiy comments

Results 454 comments of


                                            Dmitry Belyavskiy

Design document of using opaque object as symmetric key

A follow-up to #21355

Design document of using opaque object as symmetric key

I believe that we may have both exportable keys (that can be made compatible with the byte array export/import operation) and non-exportable (we got an opaque object from the provider...

Design document of using opaque object as symmetric key

> So, listening to what's been said, it sounds like an EVP_SKEY would conceptually be a union of "a bunch of bytes" (with no particular algorithm in mind) and a...

Design document of using opaque object as symmetric key

Thanks for the clarification! I totally agree with the expanded explanation.

Design document of using opaque object as symmetric key

@levitte @t8m I incorporated your comments into the updated version of the document, feel free to raise the concerns

Design document of using opaque object as symmetric key

I still wonder if we shouldn't throw it away an use EVP_PKEY instead :)

Design document of using opaque object as symmetric key

Pushed an updated version.

Design document of using opaque object as symmetric key

Some param names to be standardized: - algorithm name - key length - key representation on export (raw/wrapped/handle)

Design document of using opaque object as symmetric key

Superseded by #25908

Cipher State Serialization

> If I understand correctly, this is already possible (*) by using the EVP_CIPHER_CTX_get_updated_iv() API and the raw key; EVP_CipherInit() using the "updated" IV would then be able to resume...