OASIS PKCS 11 TC

 View Only
  • 1.  Groups - AES GCM AEAD update draft 3 uploaded

    Posted 04-10-2017 20:51
    Submitter's message This is an update to the AEAD to handle the comments from the previous call, namely a desire to have a way to handle externally generated IV's.

    I implemented this generally by creating a Generator Function parameter and defining 4 generator operations. In the future more could be added (like tls 1.3 if it differs from any of the existing generators).


    I only require the generic generator to be implemented. I also allow that the application can provide the fixed portion of the IV/nonce as well as a new parameter to specify how long the fixed portion is in bits.

    bob -- Mr. Robert Relyea Document Name : AES GCM AEAD update draft 3 No description provided. Download Latest Revision Public Download Link Submitter : Mr. Robert Relyea Group : OASIS PKCS 11 TC Folder : Working Drafts Date submitted : 2017-04-10 13:50:23


  • 2.  RE: [pkcs11] Groups - AES GCM AEAD update draft 3 uploaded

    Posted 04-11-2017 14:40
      |   view attached
    Hey Bob,   I’ve attached a version of your document with some comments added.   Let me know what you think,   Thanks,   -Dave   From: pkcs11@lists.oasis-open.org [mailto:pkcs11@lists.oasis-open.org] On Behalf Of Robert Relyea Sent: April-10-17 4:51 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] Groups - AES GCM AEAD update draft 3 uploaded   Submitter's message This is an update to the AEAD to handle the comments from the previous call, namely a desire to have a way to handle externally generated IV's. I implemented this generally by creating a Generator Function parameter and defining 4 generator operations. In the future more could be added (like tls 1.3 if it differs from any of the existing generators). I only require the generic generator to be implemented. I also allow that the application can provide the fixed portion of the IV/nonce as well as a new parameter to specify how long the fixed portion is in bits. bob -- Mr. Robert Relyea Document Name : AES GCM AEAD update draft 3 No description provided. Download Latest Revision Public Download Link Submitter : Mr. Robert Relyea Group : OASIS PKCS 11 TC Folder : Working Drafts Date submitted : 2017-04-10 13:50:23   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. Attachment: aes_gcm_proposal_DG_feedback.doc Description: aes_gcm_proposal_DG_feedback.doc

    Attachment(s)



  • 3.  Re: [pkcs11] Groups - AES GCM AEAD update draft 3 uploaded

    Posted 04-11-2017 19:00
    On 04/11/2017 07:40 AM, Gascon David wrote: Hey Bob,   I’ve attached a version of your document with some comments added.   Let me know what you think,   Thanks,   -Dave Thanks Dave.RE 'Zero is always acceptable' is just missing a period. It relates to the value of ulIvFixedBits in the previous sentence. GMAC comments. I did not change this section, so I would prefer to handle any issues there separatelyfrom the AES GCM part of the spec. I think you did identify at least issues with the existing spec, as well as possible enhancements to GMAC itself. I certainly would entertain a proposal to independently update the GMAC portion of the spec.;). bob   From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Robert Relyea Sent: April-10-17 4:51 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] Groups - AES GCM AEAD update draft 3 uploaded   Submitter's message This is an update to the AEAD to handle the comments from the previous call, namely a desire to have a way to handle externally generated IV's. I implemented this generally by creating a Generator Function parameter and defining 4 generator operations. In the future more could be added (like tls 1.3 if it differs from any of the existing generators). I only require the generic generator to be implemented. I also allow that the application can provide the fixed portion of the IV/nonce as well as a new parameter to specify how long the fixed portion is in bits. bob -- Mr. Robert Relyea Document Name : AES GCM AEAD update draft 3 No description provided. Download Latest Revision Public Download Link Submitter : Mr. Robert Relyea Group : OASIS PKCS 11 TC Folder : Working Drafts Date submitted : 2017-04-10 13:50:23   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.


  • 4.  RE: [pkcs11] Groups - AES GCM AEAD update draft 3 uploaded

    Posted 04-11-2017 19:02
    I’m good with a separate proposal to address the GMAC issues J   -Dave   From: Robert Relyea [mailto:rrelyea@REDHAT.COM] Sent: April-11-17 3:00 PM To: Gascon David <david.gascon@gemalto.com>; pkcs11@lists.oasis-open.org Subject: Re: [pkcs11] Groups - AES GCM AEAD update draft 3 uploaded   On 04/11/2017 07:40 AM, Gascon David wrote: Hey Bob,   I’ve attached a version of your document with some comments added.   Let me know what you think,   Thanks,   -Dave Thanks Dave.RE 'Zero is always acceptable' is just missing a period. It relates to the value of ulIvFixedBits in the previous sentence. GMAC comments. I did not change this section, so I would prefer to handle any issues there separatelyfrom the AES GCM part of the spec. I think you did identify at least issues with the existing spec, as well as possible enhancements to GMAC itself. I certainly would entertain a proposal to independently update the GMAC portion of the spec.;). bob   From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Robert Relyea Sent: April-10-17 4:51 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] Groups - AES GCM AEAD update draft 3 uploaded   Submitter's message This is an update to the AEAD to handle the comments from the previous call, namely a desire to have a way to handle externally generated IV's. I implemented this generally by creating a Generator Function parameter and defining 4 generator operations. In the future more could be added (like tls 1.3 if it differs from any of the existing generators). I only require the generic generator to be implemented. I also allow that the application can provide the fixed portion of the IV/nonce as well as a new parameter to specify how long the fixed portion is in bits. bob -- Mr. Robert Relyea Document Name : AES GCM AEAD update draft 3 No description provided. Download Latest Revision Public Download Link Submitter : Mr. Robert Relyea Group : OASIS PKCS 11 TC Folder : Working Drafts Date submitted : 2017-04-10 13:50:23   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.   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.


  • 5.  Re: [pkcs11] Groups - AES GCM AEAD update draft 3 uploaded

    Posted 04-11-2017 19:02
    On 04/11/2017 07:40 AM, Gascon David wrote: Hey Bob,   I’ve attached a version of your document with some comments added.   Let me know what you think,   Thanks,   -Dave Oops, I missed the last comment: Are these two fields also meant to be in the structure above? yes, that's a bug, I'll get an update with this and the missing period (maybe clearer text) shortly. Thanks, bob   From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Robert Relyea Sent: April-10-17 4:51 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] Groups - AES GCM AEAD update draft 3 uploaded   Submitter's message This is an update to the AEAD to handle the comments from the previous call, namely a desire to have a way to handle externally generated IV's. I implemented this generally by creating a Generator Function parameter and defining 4 generator operations. In the future more could be added (like tls 1.3 if it differs from any of the existing generators). I only require the generic generator to be implemented. I also allow that the application can provide the fixed portion of the IV/nonce as well as a new parameter to specify how long the fixed portion is in bits. bob -- Mr. Robert Relyea Document Name : AES GCM AEAD update draft 3 No description provided. Download Latest Revision Public Download Link Submitter : Mr. Robert Relyea Group : OASIS PKCS 11 TC Folder : Working Drafts Date submitted : 2017-04-10 13:50:23   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.