OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

pkcs11 message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: SHA3/SHAKE key derivation mechanisms naming



The next time a SE says you don’t understand PKCS11, I am going to point them to the damn RFC… btw I get to vote on this.  Member of Oasis.




From: pkcs11@lists.oasis-open.org [mailto:pkcs11@lists.oasis-open.org] On Behalf Of Daniel Minder
Sent: Tuesday, July 02, 2019 10:47 AM
To: pkcs11@lists.oasis-open.org
Subject: [EXTERNAL] [pkcs11] SHA3/SHAKE key derivation mechanisms naming




In the 3.0 mechanism draft sections 2.28 – 2.32 the key derivation mechanisms are called CKM_SHA3_xxx_KEY_DERIVATION and CKM_SHAKE_xxx_KEY_DERIVATION while in pkcs11t.h they are called CKM_SHA3_xxx_KEY_DERIVE and CKM_SHAKE_xxx_KEY_DERIVE. For consistency, it should be DERIVATION, i.e. the header file needs to be changed.







Utimaco IS GmbH
Germanusstr. 4, D.52080 Aachen, Germany, Tel: +49-241-1696-0, www.utimaco.com
Seat: Aachen – Registergericht Aachen HRB 18922
VAT ID No.: DE 815 496 496
Managementboard: Stefan Auerbach (Chairman) CEO, Malte Pollmann CSO, Dr. Frank J. Nellissen CFO

This communication is confidential. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorised and prohibited. Please inform us immediately and destroy the email.

**NOTICE: This e-mail message, including any attachments hereto, is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information. If you are not the intended recipient(s), any unauthorized review, use, copying, disclosure or distribution is prohibited. If you are not the intended recipient(s), please contact the sender by reply e-mail immediately and destroy the original and all copies (including electronic versions) of this message and any of its attachments.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]