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.

Sign up for GitHub

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

Jump to bottom

Check on the CI that Parsec is actually called #19

Closed
hug-dev opened this issue Mar 4, 2021 · 0 comments · Fixed by #20
Closed

Check on the CI that Parsec is actually called #19

hug-dev opened this issue Mar 4, 2021 · 0 comments · Fixed by #20
Assignees
@hug-dev
Labels
bug Something isn't working

Comments

@hug-dev
Copy link
Member

hug-dev commented Mar 4, 2021

If something went wrong with the SE driver registration, it is possible that Mbed Crypto is called for crypto operations instead of Parsec. We should check that Parsec is actually called.
This could be done via ./parsec-tool list-keys checking that the result is not empty.
@hug-dev hug-dev added the bug Something isn't working label Mar 4, 2021
@hug-dev hug-dev self-assigned this Mar 4, 2021
@hug-dev hug-dev mentioned this issue Mar 4, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@hug-dev hug-dev

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Check if Parsec was indeed used hug-dev/parsec-se-driver
1 participant
@hug-dev