[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [pkcs11] Groups - AEAD proposal draft 3 uploaded
On 11/14/2016 06:47 AM, Gardiner Michael wrote:
I'd also like to see the ability to do single part operations via a single API call. -Mike
The traditional interfaces (PK11_Encrypt) already supports this.The multi-group is needed for most streamed AEAD proposals since you need to keep state between the operations for:
1) caching of key setup. 2) keeping state for IV generation (needed for FIPS compliance).Both of these need to have at least an Init to set up the context and a Finalize to close up the context
bob(Tim suggested we add this to the usage guide. I can also probably add it to the documentation).
-----Original Message----- From: pkcs11@lists.oasis-open.org [mailto:pkcs11@lists.oasis-open.org] On Behalf Of Johnson Darren Sent: November-14-16 9:43 AM To: valerie.fenwick@oracle.com; rrelyea@redhat.com; pkcs11@lists.oasis-open.org Subject: RE: [pkcs11] Groups - AEAD proposal draft 3 uploaded I think this is a good idea. I think we should also consider supporting a similar single part API for some of the existing APIs (ie C_Encrypt, C_Sign...). DJ -----Original Message----- From: pkcs11@lists.oasis-open.org [mailto:pkcs11@lists.oasis-open.org] On Behalf Of Valerie Fenwick Sent: Monday, November 14, 2016 6:14 AM To: Robert Relyea <rrelyea@redhat.com>; pkcs11@lists.oasis-open.org Subject: Re: [pkcs11] Groups - AEAD proposal draft 3 uploaded As you might be able to tell, doing in person meetings with some of my crypto heads this week :-) Question came up: Why can't we have a truly "single operation" call? That is, combine: • C_MessageEncryptInit and • C_EncryptMessage So it's only necessary to call "C_EncryptMessage" as a truly single call? That way, the library implementing the functions will also know from the first call that this is a single part operation and can act accordingly? This may have come up, and I may have just forgotten... thanks! Valerie On 7/21/2016 10:30 PM, Robert Relyea wrote:/Submitter's message/ Fix numerous typos. Make the Requirement to call C_MessageXXXXInit() explicit in the descriptions of C_XXXXMessage() and CXXXXMessgeBegin Fix conflicting flag values. This should address most of the comments I received on AEAD -- Mr. Robert Relyea *Document Name*: AEAD proposal draft 3 <https://www.oasis-open.org/apps/org/workgroup/pkcs11/document.php?doc ument_id=58565> ---------------------------------------------------------------------- ---------- *Description* Fix numerous typos. Make the Requirement to call C_MessageXXXXInit() explicit in the descriptions of C_XXXXMessage() and CXXXXMessgeBegin Fix conflicting flag values. This should address most of the comments I received on AEAD Download Latest Revision <https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/585 65/latest/AEAD_proposal.doc> Public Download Link <https://www.oasis-open.org/committees/document.php?document_id=58565& wg_abbrev=pkcs11> ---------------------------------------------------------------------- ---------- *Submitter*: Mr. Robert Relyea *Group*: OASIS PKCS 11 TC *Folder*: Working Drafts *Date submitted*: 2016-07-21 15:30:21-- Valerie Fenwick, http://bubbva.blogspot.com/ @bubbva Solaris Cryptographic & Key Management Technologies, Manager Oracle Corporation: 4180 Network Circle, Santa Clara, CA, 95054. --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php ________________________________ This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited. E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender. Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]