OASIS PKCS 11 TC

 View Only
Expand all | Collapse all

PKCS#11 missing or incorrect definitions

  • 1.  PKCS#11 missing or incorrect definitions

    Posted 06-20-2014 20:01
    So rather than just complain, I've put together a list of all the incorrect, mispelled, or missing definitions/constants in the PKCS#11 v2.40 spec: https://wiki.oasis-open.org/pkcs11/Definitions About 40 missing and 40 incorrect/misspelled. Hope this is helpful. Cheers, Stef


  • 2.  Re: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 06-20-2014 20:43
    On 06/20/14 01:00 PM, Stef Walter wrote: So rather than just complain, I've put together a list of all the incorrect, mispelled, or missing definitions/constants in the PKCS#11 v2.40 spec: https://wiki.oasis-open.org/pkcs11/Definitions About 40 missing and 40 incorrect/misspelled. Hope this is helpful. Thank you for collecting these. Looks like a good start on the "errata" document we were saying we might need. spell checkers never find this stuff. I'm afraid we will now start finding more things now that we're all digging into implementation that we just didn't see no matter how many times we looked at the text. Valerie -- Valerie Fenwick, http://bubbva.blogspot.com/ @bubbva Solaris Cryptographic & Key Management Technologies, Manager Oracle Corporation: 4180 Network Circle, Santa Clara, CA, 95054.


  • 3.  RE: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 06-23-2014 15:57
    Hi Stef Thanks for doing this. I've gone through each of these items and corrected where possible. I'm going to review once more later today and then post an updated CSD. Thanks --Chris -----Original Message----- From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Stef Walter Sent: Friday, June 20, 2014 4:00 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] PKCS#11 missing or incorrect definitions So rather than just complain, I've put together a list of all the incorrect, mispelled, or missing definitions/constants in the PKCS#11 v2.40 spec: https://wiki.oasis-open.org/pkcs11/Definitions About 40 missing and 40 incorrect/misspelled. Hope this is helpful. Cheers, Stef --------------------------------------------------------------------- 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


  • 4.  Re: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 06-23-2014 16:16
    Thanks Stef and Chris. Chris, Can you also take a look at this issue ? https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/49138/ballot_2399.html From the above ballot, we agree to define a new structure for CK_PKCS5_PBKD2_PARAMS. I am looking for this new structure definition in oasis-open.org, but I could not find it. I don't even know the new name. Do you know how does this newly defined structure looks like for v2.40 ? Thanks! Best, Oscar On 06/23/14 08:57 AM, Chris Zimman wrote: Hi Stef Thanks for doing this. I've gone through each of these items and corrected where possible. I'm going to review once more later today and then post an updated CSD. Thanks --Chris -----Original Message----- From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Stef Walter Sent: Friday, June 20, 2014 4:00 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] PKCS#11 missing or incorrect definitions So rather than just complain, I've put together a list of all the incorrect, mispelled, or missing definitions/constants in the PKCS#11 v2.40 spec: https://wiki.oasis-open.org/pkcs11/Definitions About 40 missing and 40 incorrect/misspelled. Hope this is helpful. Cheers, Stef --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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


  • 5.  RE: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 06-23-2014 17:36
    Hi Oscar Here's what we have right now in the CDS: * CK_ PKCS5_PBKD2_PARAMS; CK_PKCS5_PBKD2_PARAMS_PTR CK_PKCS5_PBKD2_PARAMS is a structure that provides the parameters to the CKM_PKCS5_PBKD2 mechanism. The structure is defined as follows: typedef struct CK_PKCS5_PBKD2_PARAMS { CK_PKCS5_PBKDF2_SALT_SOURCE_TYPE saltSource; CK_VOID_PTR pSaltSourceData; CK_ULONG ulSaltSourceDataLen; CK_ULONG iterations; CK_PKCS5_PBKD2_PSEUDO_RANDOM_FUNCTION_TYPE prf; CK_VOID_PTR pPrfData; CK_ULONG ulPrfDataLen; CK_UTF8CHAR_PTR pPassword; CK_ULONG_PTR ulPasswordLen; } CK_PKCS5_PBKD2_PARAMS; The fields of the structure have the following meanings: saltSource source of the salt value pSaltSourceData data used as the input for the salt source ulSaltSourceDataLen length of the salt source input iterations number of iterations to perform when generating each block of random data prf pseudo-random function used to generate the key pPrfData data used as the input for PRF in addition to the salt value ulPrfDataLen length of the input data for the PRF pPassword points to the password to be used in the PBE key generation ulPasswordLen length in bytes of the password information CK_PKCS5_PBKD2_PARAMS_PTR is a pointer to a CK_PKCS5_PBKD2_PARAMS. What is being proposed for change here? I looked at the straw poll, but it's not entirely clear to me. Thanks --Chris -----Original Message----- From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Oscar So Sent: Monday, June 23, 2014 12:16 PM To: pkcs11@lists.oasis-open.org Subject: Re: [pkcs11] PKCS#11 missing or incorrect definitions Thanks Stef and Chris. Chris, Can you also take a look at this issue ? https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/49138/ballot_2399.html From the above ballot, we agree to define a new structure for CK_PKCS5_PBKD2_PARAMS. I am looking for this new structure definition in oasis-open.org, but I could not find it. I don't even know the new name. Do you know how does this newly defined structure looks like for v2.40 ? Thanks! Best, Oscar On 06/23/14 08:57 AM, Chris Zimman wrote: > Hi Stef > > Thanks for doing this. I've gone through each of these items and corrected where possible. I'm going to review once more later today and then post an updated CSD. > > Thanks > > --Chris > > -----Original Message----- > From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] > On Behalf Of Stef Walter > Sent: Friday, June 20, 2014 4:00 PM > To: pkcs11@lists.oasis-open.org > Subject: [pkcs11] PKCS#11 missing or incorrect definitions > > So rather than just complain, I've put together a list of all the > incorrect, mispelled, or missing definitions/constants in the PKCS#11 > v2.40 spec: > > https://wiki.oasis-open.org/pkcs11/Definitions > > About 40 missing and 40 incorrect/misspelled. Hope this is helpful. > > Cheers, > > Stef > > --------------------------------------------------------------------- > 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 > > > --------------------------------------------------------------------- > 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 > --------------------------------------------------------------------- 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


  • 6.  Re: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 06-23-2014 18:28
    Hi Chris, The issue is with: CK_ULONG_PTR ulPasswordLen; in CK_PKCS5_PBKD2_PARAMS. It should not be a pointer to ULONG. It should just be: CK_ULONG ulPasswordLen; The straw poll suggested that we should NOT change "CK_ULONG_PTR ulPasswordLen" inside CK_PKCS5_PBKD2_PARAMS, we should define a NEW struct for CK_PKCS5_PBKD2_PARAMS. And, we should deprecate CK_PKCS5_PBKD2_PARAMS. Refer to: https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/49138/ballot_2399.html?referring_url=%2Fkws "Create new mechanism/structure and deprecating existing. 28 84 28/33" BUT, I could not find where this NEW struct is ? Thanks, Oscar On 06/23/14 10:35 AM, Chris Zimman wrote: Hi Oscar Here's what we have right now in the CDS: * CK_ PKCS5_PBKD2_PARAMS; CK_PKCS5_PBKD2_PARAMS_PTR CK_PKCS5_PBKD2_PARAMS is a structure that provides the parameters to the CKM_PKCS5_PBKD2 mechanism. The structure is defined as follows: typedef struct CK_PKCS5_PBKD2_PARAMS { CK_PKCS5_PBKDF2_SALT_SOURCE_TYPE saltSource; CK_VOID_PTR pSaltSourceData; CK_ULONG ulSaltSourceDataLen; CK_ULONG iterations; CK_PKCS5_PBKD2_PSEUDO_RANDOM_FUNCTION_TYPE prf; CK_VOID_PTR pPrfData; CK_ULONG ulPrfDataLen; CK_UTF8CHAR_PTR pPassword; CK_ULONG_PTR ulPasswordLen; } CK_PKCS5_PBKD2_PARAMS; The fields of the structure have the following meanings: saltSource source of the salt value pSaltSourceData data used as the input for the salt source ulSaltSourceDataLen length of the salt source input iterations number of iterations to perform when generating each block of random data prf pseudo-random function used to generate the key pPrfData data used as the input for PRF in addition to the salt value ulPrfDataLen length of the input data for the PRF pPassword points to the password to be used in the PBE key generation ulPasswordLen length in bytes of the password information CK_PKCS5_PBKD2_PARAMS_PTR is a pointer to a CK_PKCS5_PBKD2_PARAMS. What is being proposed for change here? I looked at the straw poll, but it's not entirely clear to me. Thanks --Chris -----Original Message----- From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Oscar So Sent: Monday, June 23, 2014 12:16 PM To: pkcs11@lists.oasis-open.org Subject: Re: [pkcs11] PKCS#11 missing or incorrect definitions Thanks Stef and Chris. Chris, Can you also take a look at this issue ? https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/49138/ballot_2399.html From the above ballot, we agree to define a new structure for CK_PKCS5_PBKD2_PARAMS. I am looking for this new structure definition in oasis-open.org, but I could not find it. I don't even know the new name. Do you know how does this newly defined structure looks like for v2.40 ? Thanks! Best, Oscar On 06/23/14 08:57 AM, Chris Zimman wrote: Hi Stef Thanks for doing this. I've gone through each of these items and corrected where possible. I'm going to review once more later today and then post an updated CSD. Thanks --Chris -----Original Message----- From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Stef Walter Sent: Friday, June 20, 2014 4:00 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] PKCS#11 missing or incorrect definitions So rather than just complain, I've put together a list of all the incorrect, mispelled, or missing definitions/constants in the PKCS#11 v2.40 spec: https://wiki.oasis-open.org/pkcs11/Definitions About 40 missing and 40 incorrect/misspelled. Hope this is helpful. Cheers, Stef --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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


  • 7.  RE: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 06-23-2014 18:55
    Hi Oscar Right, I follow you there. I was missing where the new struct was as well. Thanks --Chris -----Original Message----- From: Oscar So [ mailto:oscar.so@oracle.com ] Sent: Monday, June 23, 2014 2:28 PM To: Chris Zimman Cc: pkcs11@lists.oasis-open.org Subject: Re: [pkcs11] PKCS#11 missing or incorrect definitions Hi Chris, The issue is with: CK_ULONG_PTR ulPasswordLen; in CK_PKCS5_PBKD2_PARAMS. It should not be a pointer to ULONG. It should just be: CK_ULONG ulPasswordLen; The straw poll suggested that we should NOT change "CK_ULONG_PTR ulPasswordLen" inside CK_PKCS5_PBKD2_PARAMS, we should define a NEW struct for CK_PKCS5_PBKD2_PARAMS. And, we should deprecate CK_PKCS5_PBKD2_PARAMS. Refer to: https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/49138/ballot_2399.html?referring_url=%2Fkws "Create new mechanism/structure and deprecating existing. 28 84 28/33" BUT, I could not find where this NEW struct is ? Thanks, Oscar On 06/23/14 10:35 AM, Chris Zimman wrote: > Hi Oscar > > Here's what we have right now in the CDS: > > * CK_ PKCS5_PBKD2_PARAMS; CK_PKCS5_PBKD2_PARAMS_PTR > CK_PKCS5_PBKD2_PARAMS is a structure that provides the parameters to the CKM_PKCS5_PBKD2 mechanism. > The structure is defined as follows: > > typedef struct CK_PKCS5_PBKD2_PARAMS { > CK_PKCS5_PBKDF2_SALT_SOURCE_TYPE saltSource; > CK_VOID_PTR pSaltSourceData; > CK_ULONG ulSaltSourceDataLen; > CK_ULONG iterations; > CK_PKCS5_PBKD2_PSEUDO_RANDOM_FUNCTION_TYPE prf; > CK_VOID_PTR pPrfData; > CK_ULONG ulPrfDataLen; > CK_UTF8CHAR_PTR pPassword; > CK_ULONG_PTR ulPasswordLen; > } CK_PKCS5_PBKD2_PARAMS; > > The fields of the structure have the following meanings: > saltSource source of the salt value > pSaltSourceData data used as the input for the salt source > ulSaltSourceDataLen length of the salt source input > iterations number of iterations to perform when generating each block of random data > prf pseudo-random function used to generate the key > pPrfData data used as the input for PRF in addition to the salt value > ulPrfDataLen length of the input data for the PRF > pPassword points to the password to be used in the PBE key generation > ulPasswordLen length in bytes of the password information > CK_PKCS5_PBKD2_PARAMS_PTR is a pointer to a CK_PKCS5_PBKD2_PARAMS. > > What is being proposed for change here? I looked at the straw poll, but it's not entirely clear to me. > > Thanks > > --Chris > > -----Original Message----- > From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] > On Behalf Of Oscar So > Sent: Monday, June 23, 2014 12:16 PM > To: pkcs11@lists.oasis-open.org > Subject: Re: [pkcs11] PKCS#11 missing or incorrect definitions > > Thanks Stef and Chris. > > > Chris, > > Can you also take a look at this issue ? > > https://www.oasis-open.org/apps/org/workgroup/pkcs11/download.php/4913 > 8/ballot_2399.html > > From the above ballot, we agree to define a new structure for CK_PKCS5_PBKD2_PARAMS. > > I am looking for this new structure definition in oasis-open.org, but I could not find it. I don't even know the new name. > > Do you know how does this newly defined structure looks like for v2.40 ? > > > Thanks! > > Best, > Oscar > > > > > > On 06/23/14 08:57 AM, Chris Zimman wrote: >> Hi Stef >> >> Thanks for doing this. I've gone through each of these items and corrected where possible. I'm going to review once more later today and then post an updated CSD. >> >> Thanks >> >> --Chris >> >> -----Original Message----- >> From: pkcs11@lists.oasis-open.org >> [ mailto:pkcs11@lists.oasis-open.org ] >> On Behalf Of Stef Walter >> Sent: Friday, June 20, 2014 4:00 PM >> To: pkcs11@lists.oasis-open.org >> Subject: [pkcs11] PKCS#11 missing or incorrect definitions >> >> So rather than just complain, I've put together a list of all the >> incorrect, mispelled, or missing definitions/constants in the PKCS#11 >> v2.40 spec: >> >> https://wiki.oasis-open.org/pkcs11/Definitions >> >> About 40 missing and 40 incorrect/misspelled. Hope this is helpful. >> >> Cheers, >> >> Stef >> >> --------------------------------------------------------------------- >> 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.ph >> p >> >> >> --------------------------------------------------------------------- >> 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.ph >> p >> > > > --------------------------------------------------------------------- > 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 >


  • 8.  Re: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 06-23-2014 16:58
    Hi all, Just wanted to note that the numbering and cross-references among the Tables and Figures also need to be checked methodically.  Good examples of the problems are: - In "Current Mechanisms", there are a number of references to "Table 15" in the Base specification, but actually, that is now Table 10.  I think this happens in others as well... - In "Current Mechanisms" (at least - I think it is likely in the others), the numbering of the tables has been corrupted by the inconsistent use of numbering fields in the .DOC source.  This shows up easily in the PDF and HTML versions... so for instance, in the PDF, Table 15 is followed by Table 167, then 178.  (Many other examples.) In some cases numbering fields overlap with manually-inserted (static) numbers. Note particularly that this will require the document Editor to display all field markings in MS-Word, and understand how they are used.  To display them, in Word 2010, for example, use: File --> Options --> Advanced --> Field Shading (set to Always).  If these numbering fields are properly set up, they will automatically update the numbering, and adjust any (same-document) references. Also, it will be easy to generate a Table of Figures and Table of Tables (if wanted) to help users navigate the document. Best regards, Paul  On Mon, Jun 23, 2014 at 11:57 AM, Chris Zimman < czimman@bloomberg.com > wrote: Hi Stef Thanks for doing this.  I've gone through each of these items and corrected where possible.  I'm going to review once more later today and then post an updated CSD. Thanks --Chris -----Original Message----- From: pkcs11@lists.oasis-open.org [mailto: pkcs11@lists.oasis-open.org ] On Behalf Of Stef Walter Sent: Friday, June 20, 2014 4:00 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] PKCS#11 missing or incorrect definitions So rather than just complain, I've put together a list of all the incorrect, mispelled, or missing definitions/constants in the PKCS#11 v2.40 spec: https://wiki.oasis-open.org/pkcs11/Definitions About 40 missing and 40 incorrect/misspelled. Hope this is helpful. Cheers, Stef --------------------------------------------------------------------- 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 --------------------------------------------------------------------- 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 -- Paul Knight   - Tel: +1 781-861-1013 OASIS - Advancing open standards for the information society Document Process Analyst


  • 9.  RE: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 06-23-2014 19:33
      |   view attached
    Hi Stef Would you mind taking a look at this revision? I've tried to correct as many of the items you've pointed out as I could. Thanks --Chris -----Original Message----- From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Stef Walter Sent: Friday, June 20, 2014 4:00 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] PKCS#11 missing or incorrect definitions So rather than just complain, I've put together a list of all the incorrect, mispelled, or missing definitions/constants in the PKCS#11 v2.40 spec: https://wiki.oasis-open.org/pkcs11/Definitions About 40 missing and 40 incorrect/misspelled. Hope this is helpful. Cheers, Stef --------------------------------------------------------------------- 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 Attachment: pkcs11-curr-v2.40-csprd05.doc Description: pkcs11-curr-v2.40-csprd05.doc

    Attachment(s)

    doc
    pkcs11-curr-v2.40-csprd05.doc   1.92 MB 1 version


  • 10.  RE: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 06-24-2014 17:21
    Dina found another typo, and I corrected two more as well. I'm waiting for feedback before publishing the next CDS.


  • 11.  Re: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 07-01-2014 16:26
    This is a painstaking process. I was unable to see any revisions in the document, nor find the original document that you edited so (in order to use a compare document feature). but I finally found time to complete it. It's real a shame we aren't using modern tools such as distributed revision control and a textual diffable non-proprietary format. I updated the page here with the current list of problems I've found: https://wiki.oasis-open.org/pkcs11/Definitions * 14 definitions remain undocumented or misspelled * A few less than 40 constant definitions are missing. * Also noticed extra 'C' character typo in "2.2.1 Definitions". * CKM_AES_CMAC_GENERAL continues to conflict with v2.30 CKM_AES_CTS Hope that's a help. Stef On 23.06.2014 21:32, Chris Zimman wrote: > Hi Stef > > Would you mind taking a look at this revision? I've tried to correct as many of the items you've pointed out as I could. > > Thanks > > --Chris > > -----Original Message----- > From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Stef Walter > Sent: Friday, June 20, 2014 4:00 PM > To: pkcs11@lists.oasis-open.org > Subject: [pkcs11] PKCS#11 missing or incorrect definitions > > So rather than just complain, I've put together a list of all the incorrect, mispelled, or missing definitions/constants in the PKCS#11 > v2.40 spec: > > https://wiki.oasis-open.org/pkcs11/Definitions > > About 40 missing and 40 incorrect/misspelled. Hope this is helpful. > > Cheers, > > Stef > > --------------------------------------------------------------------- > 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 > > > > > --------------------------------------------------------------------- > 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 >


  • 12.  RE: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 07-02-2014 17:02
    Hi Stef I believe I've corrected all of the remaining items on the list. With respect to the item about CKM_AES_KEY_WRAP/CKM_AES_KEY_WRAP_PAD, in v2.30 there was a collision: #define CKM_AES_KEY_WRAP 0x00001090 #define CKM_AES_KEY_WRAP_PAD 0x00001091 #define CKM_BLOWFISH_KEY_GEN 0x00001090 #define CKM_BLOWFISH_CBC 0x00001091 I've fixed these in the latest CDS. Thanks --Chris -----Original Message----- From: Stef Walter [ mailto:stefw@redhat.com ] Sent: Tuesday, July 01, 2014 12:26 PM To: Chris Zimman; pkcs11@lists.oasis-open.org Subject: Re: [pkcs11] PKCS#11 missing or incorrect definitions This is a painstaking process. I was unable to see any revisions in the document, nor find the original document that you edited so (in order to use a compare document feature). but I finally found time to complete it. It's real a shame we aren't using modern tools such as distributed revision control and a textual diffable non-proprietary format. I updated the page here with the current list of problems I've found: https://wiki.oasis-open.org/pkcs11/Definitions * 14 definitions remain undocumented or misspelled * A few less than 40 constant definitions are missing. * Also noticed extra 'C' character typo in "2.2.1 Definitions". * CKM_AES_CMAC_GENERAL continues to conflict with v2.30 CKM_AES_CTS Hope that's a help. Stef On 23.06.2014 21:32, Chris Zimman wrote: > Hi Stef > > Would you mind taking a look at this revision? I've tried to correct as many of the items you've pointed out as I could. > > Thanks > > --Chris > > -----Original Message----- > From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] > On Behalf Of Stef Walter > Sent: Friday, June 20, 2014 4:00 PM > To: pkcs11@lists.oasis-open.org > Subject: [pkcs11] PKCS#11 missing or incorrect definitions > > So rather than just complain, I've put together a list of all the > incorrect, mispelled, or missing definitions/constants in the PKCS#11 > v2.40 spec: > > https://wiki.oasis-open.org/pkcs11/Definitions > > About 40 missing and 40 incorrect/misspelled. Hope this is helpful. > > Cheers, > > Stef > > --------------------------------------------------------------------- > 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 > > > > > --------------------------------------------------------------------- > 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 >


  • 13.  Re: [pkcs11] PKCS#11 missing or incorrect definitions

    Posted 07-16-2014 18:43
    On 07/ 1/14 09:25 AM, Stef Walter wrote: This is a painstaking process. I was unable to see any revisions in the document, nor find the original document that you edited so (in order to use a compare document feature). but I finally found time to complete it. It's real a shame we aren't using modern tools such as distributed revision control and a textual diffable non-proprietary format. Perhaps we could consider a different format for v3.0? Obviously there would be conversion issues, but may be worth proposing. Valerie I updated the page here with the current list of problems I've found: https://wiki.oasis-open.org/pkcs11/Definitions * 14 definitions remain undocumented or misspelled * A few less than 40 constant definitions are missing. * Also noticed extra 'C' character typo in "2.2.1 Definitions". * CKM_AES_CMAC_GENERAL continues to conflict with v2.30 CKM_AES_CTS Hope that's a help. Stef On 23.06.2014 21:32, Chris Zimman wrote: Hi Stef Would you mind taking a look at this revision? I've tried to correct as many of the items you've pointed out as I could. Thanks --Chris -----Original Message----- From: pkcs11@lists.oasis-open.org [ mailto:pkcs11@lists.oasis-open.org ] On Behalf Of Stef Walter Sent: Friday, June 20, 2014 4:00 PM To: pkcs11@lists.oasis-open.org Subject: [pkcs11] PKCS#11 missing or incorrect definitions So rather than just complain, I've put together a list of all the incorrect, mispelled, or missing definitions/constants in the PKCS#11 v2.40 spec: https://wiki.oasis-open.org/pkcs11/Definitions About 40 missing and 40 incorrect/misspelled. Hope this is helpful. Cheers, Stef