OASIS PKCS 11 TC

 View Only

  • 1.  Restructure-PKCS11-SHA_v2.docx uploaded

    Posted 07-15-2025 14:00
    Submitter's message
    All,
    this is an update to proposal https://groups.oasis-open.org/higherlogic/ws/public/document?document_id=72890&wg_id=922ef643-1e10-4d65-a5ea-018dc7d3f0a4 , now restructuring sections for SHA, SHAKE and BLAKE2B. It does not yet cover digest function and HMAC function for GOST R34.11 because a) of lack of time and b) GOST is a bit different as it has a mechanism parameter structure which other digest functions don't have.
    Because of the latter, we might even discuss whether it makes sense / is helpful to include GOST R34.11 in such restructuring, or rather leave it as it is. Any thoughts?

    Thanks,
    Dieter
    -- Mr. Dieter Bong
    Document Name: Restructure-PKCS11-SHA_v2.docx
    Description
    Update to proposal
    https://groups.oasis-open.org/higherlogic/ws/public/document?document_id=72890&wg_id=922ef643-1e10-4d65-a5ea-018dc7d3f0a4
    , now restructuring sections for SHA, SHAKE and BLAKE2B.
    Download Latest Revision
    Public Download Link
    Submitter: Mr. Dieter Bong
    Group: OASIS PKCS 11 TC
    Folder: Working Drafts
    Date submitted: 2025-07-15 17:59:29


    ---------------------------------
    Best regards,
    Dieter
    ---------------------------------


  • 2.  RE: Restructure-PKCS11-SHA_v2.docx uploaded

    Posted 07-15-2025 14:19
    It may make sense to just have *all* GOST related mechanisms in their
    own section, they are rarely used in practice by most of our users and
    being a national, rather than international, standard it may make sense
    to segregate them to a specific section that says so.

    Simo.

    --
    Simo Sorce
    Distinguished Engineer
    RHEL Crypto Team
    Red Hat, Inc


    Original Message


Related Content