-
Notifications
You must be signed in to change notification settings - Fork 47
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
Refactor setup #436
Refactor setup #436
Conversation
NOTE: Kryoptic stuff will fail until latchset/kryoptic#84 is merged |
0209be8
to
d83eace
Compare
NOTE: softoken fails on Centos9 because it does not support NSS_LIB_PARAMS yet I think ... |
@Jakuje what should we do with NSS on CentOS 9 ? |
Probably yes. I think CentOS 9 should get the NSS update any time soon (I thought this already some months back though). |
8dd5cff
to
d51d251
Compare
@Jakuje Best I could do is to make the C9s test "pass" without actually doing anything if the NSS version is too old. |
82f466a
to
6212f8b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one last comment, otherwise consider approved.
Move only the token specific initialization into custom setup files, and the use pkcs11-tool and a single script to set up all the keys and certificates. Signed-off-by: Simo Sorce <[email protected]>
Unfortunately there does not seem to be a real way to skip the test, this just marks it as pass without doing nothing. Hopefully we can drop this special case soon as c9s get's a new version of NSS. Signed-off-by: Simo Sorce <[email protected]>
Signed-off-by: Simo Sorce <[email protected]>
Thanks for the review @Jakuje |
Move only the token specific initialization into custom setup files, and the use pkcs11-tool and a single script to set up all the keys and certificates.
Description
The main work of setting up tokens is now in test/setup.sh and each token type has a -init.sh file that does the bare minimum custom initialization needed.
Checklist
[ ] Code modified for feature[ ] Test suite updated with negative tests[ ] Documentation updatedReviewer's checklist:
[ ] Any issues marked for closing are addressed[ ] This feature/change has adequate documentation added[ ] Coverity Scan has run if needed (code PR) and no new defects were found