microsoft / microsoft/SymCrypt

Is the Session API within the approved scope of CMVP certificate #5313?

Open
#60 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
890
Forks
91
PR merge metrics
No merged PRs in 30d

Description

libsymcrypt.so exports SymCryptSessionSenderInit, SymCryptSessoinReceiverInit, SymCryptSessionGcmEncrypt, SymCryptSessionGcmDecrypt and SymCryptSessionDestroy (VERSION_101.). The 101.2.0 changelog describes these as enabling "multithreaded IV generation within the SymCrypt FIPS boundary."

The #5313 Security Policy does not name a Session service in its services table, and registers IV Generation - External for AES-GCM. The certificate seperately claims IG C.H Scenario 3.

When a caller uses SymCryptSessionSenderInit followed by SymCryptSessionGcmEncrypt, so that the module constructs and increments the nonce internally, is that an approved-mode use of the module under #5313? Does it satisfy the Scenario 3 claim?

Trying to understand so we can use the module in approved mode correctly. Thanks!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked #5313 Security Policy, especially its services table, AES-GCM IV Generation - External entry, and IG C.H Scenario 3 claim; then compare those statements with the 101.2.0 changelog and the listed Session API exports. Done means a maintainer clarifies whether SessionSenderInit followed by SessionGcmEncrypt is approved-mode use and satisfies Scenario 3.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
cryptography, security
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.