Skip to content

Conversation

@simo5
Copy link
Member

@simo5 simo5 commented Mar 31, 2025

Description

Fixes #191

Checklist

  • Test suite updated with functionality tests
  • Test suite updated with negative tests
  • [ ] Documentation was updated
  • [ ] This is not a code change

Reviewer's checklist:

  • Any issues marked for closing are fully addressed
  • There is a test suite reasonably covering new functionality or modifications
  • This feature/change has adequate documentation added
  • A changelog entry is added if the change is significant
  • Code conform to coding style that today cannot yet be enforced via the check style test
  • Commits have short titles and sensible text

When an operation is not initialized we need to return the
CKR_OPERATION_NOT_INITIALIZED and not CKR_GENERAL_ERROR,
this is a regression from a recent change.

Fixes latchset#191

Signed-off-by: Simo Sorce <[email protected]>
@simo5 simo5 requested a review from Jakuje March 31, 2025 16:16
Copy link
Contributor

@Jakuje Jakuje left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just typo and formatting. Otherwise lgtm

};

/* Ensure that trying to call an operation w/o initialization returns
* the propoer error
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* the propoer error
* the proper error

@simo5 simo5 merged commit 7b7c993 into latchset:main Mar 31, 2025
23 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Multi-part functions return CKR_GENERAL_ERROR when used in a non-initialized state

2 participants