Re: [pkcs11] Groups - Post Quantum Signatures Multipart solution 1 uploaded

[Robert Relyea <rrelyea@redhat.com>]

On 5/4/23 10:26 AM, Robert Relyea wrote:

>       
>       Submitter's message
>       This is the first possible proposal. Create a general mechanism
>       parameter which is only used on C_VerifyInit. If if it's not
>       supplied, only signle part operations for these mechanisms are
>       used.
>     
    The advantage of this proposal is you could implement this for 3.0
    and 3.1 tokens. The disadvantage is that you need to explicitly add
    this to each mechanism that needs it. It also generates a conflict
    with the signature passed in C_VerifyFinal/C_Verify below.

One question is what is the semantics of the signature passed to C_VerifyFinal or C_Verify if the signature parameter is supplied. The proposed semantic is the results are undefined (the application could get the wrong answer to C_VerifyFinal, or it could fail). The idea is the token would not have to keep a copy of the signature over the entire operation.
-- Mr. Robert Relyea

Document Name: Post Quantum Signatures Multipart solution 1

---

Description
General mechanism parameters to solve the multipart verify signature issue.
Download Latest Revision
Public Download Link

---

Submitter: Mr. Robert Relyea
Group: OASIS PKCS 11 TC
Folder: Working Drafts
Date submitted: 2023-05-04 10:26:22