Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use a single tool for setting up the token #418

Merged
merged 1 commit into from
Jul 22, 2024
Merged

Conversation

simo5
Copy link
Member

@simo5 simo5 commented Jul 9, 2024

Description

pkcs11-tool is well capable of initializing a token, so just use it for everything and drop use of p11tool which is quirkier.

Checklist

  • [ ] Code modified for feature
  • Test suite updated with functionality tests
  • [ ] Test suite updated with negative tests
  • [ ] Documentation updated

Reviewer's checklist:

  • [ ] Any issues marked for closing are addressed
  • There is a test suite reasonably covering new functionality or modifications
  • [ ] This feature/change has adequate documentation added
  • Code conform to coding style that today cannot yet be enforced via the check style test
  • Commits have short titles and sensible commit messages
  • [ ] Coverity Scan has run if needed (code PR) and no new defects were found

pkcs11-tool is well capable of initializing a token, so just use it for
everything and drop use of p11tool which is quirkier.

Signed-off-by: Simo Sorce <simo@redhat.com>
--label "Pkcs11 Provider Tests" --so-pin "${PINVALUE}" 2>&1
# set user pin
pkcs11-tool --module "${P11LIB}" --so-pin "${PINVALUE}" \
--login --login-type so --init-pin --pin "${PINVALUE}" 2>&1
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: whats the point of forwarding the stderr to stdout like this? Arent both of them captured the same way by the test driver?

Copy link
Member Author

Choose a reason for hiding this comment

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

They are not, I needed it to work out some issues.
But I already forgot how it exactly affected things, I think the main issue was just ordering, this way messages are in order otherwise you get all of stdout and then out of order all of stderr.

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.

otherwise lgtm

@simo5 simo5 merged commit a550306 into latchset:main Jul 22, 2024
36 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.

None yet

2 participants