OASIS PKCS 11 TC

 View Only

  • 1.  Identifier allocations for PKCS 11 v2. To be voted on Sep 11..

    Posted 08-28-2024 18:51

    results.out holds the log of the allocation run.

    all.result is a concatenation of the all the result files.

    The files are all checked into our git repository (oasis-tcs/pkcs11.git) in 'working/identifier_db/pkcs11v3.2'

    You can look at all the proposed identifiers by running './lookup.pl proposed' in 'working/identifier_db'

    I should have ran these as each proposal came in. NOTE: I've modified the allocation scheme where if you specify 'opt' in the proposal, rather then allocation from the current max identifier, it looks for the smallest unallocated identifier. For historical reasons we left a lot of holes in our allocation space, and it seems right to start filling them in.

    NOTE on process??

    1. once we approve them, I'll move the identifiers from 'proposed' to 'approved'. In the database.
    2. I'll update them in the header files and post the header file to vote on in the next meeting.
    3. I'll create a pkcs11v3.2 branch and a 3-02 tag.
    4. (after the spec has been approved I'll move all the approved identifiers to 'spec').




  • 2.  RE: Identifier allocations for PKCS 11 v2. To be voted on Sep 11..

    Posted 08-28-2024 20:52
    Update. After trying to integrate these into the header, and comparing
    with the draft spec, I found some errors in my previous proposal. I've
    included an updated all.result and an erratta.update that includes the
    difference.

    I also found a number of missing symbols I'll bring forward a separate
    proposal.


    Original Message


Related Content