[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Clarification on use of C_Encrypt() and C_Decrypt() with zero-length inputs.
Gah.. sorry about that — I was trying to edit for clarity and fat fingered the d@# Touch Bar send key. So to try it again — the underlying definition of some ciphers (btw, the AES_GCM section references [GCM] but doesn’t appear in the list of references in the mechanism doc — so I’m not sure if you’re referring to an RFC or the NIST publication here) allow for empty input data (padding variants, combined mode ciphers). What isn’t clear is if their use in PKCS#11 via C_Encrypt/Decrypt still require the pData to be set in such an instance. From: Jason King <jason.king@joyent.com> Date: January 26, 2018 at 11:05:22 AM To: pkcs11-comment@lists.oasis-open.org <pkcs11-comment@lists.oasis-open.org> Subject: Clarification on use of C_Encrypt() and C_Decrypt() with zero-length inputs.
|
Attachment:
signature.asc
Description: Message signed with OpenPGP using AMPGpg
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]