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

Quickstart 1.3.0 package does not have pkcs11-provider compiled #773

Open
arv1ndh opened this issue Aug 28, 2024 · 1 comment
Open

Quickstart 1.3.0 package does not have pkcs11-provider compiled #773

arv1ndh opened this issue Aug 28, 2024 · 1 comment

Comments

@arv1ndh
Copy link

arv1ndh commented Aug 28, 2024

Trying to checkout parsec and was following the instructions mentioned in the book to test out the pkcs11-provider, was getting this error after adding the required configs in config.toml

~/parsec_poc/quickstart-1.3.0-linux-x86_64/bin$ ./parsec -c ../quickstart/config.toml
[INFO  parsec] Parsec started. Configuring the service...
[INFO  parsec_service::key_info_managers::sqlite_manager] SQLiteKeyInfoManager - Found 0 key info mapping records
[ERROR parsec_service::utils::config] Provider (Pkcs11 { name: Some("pkcs11-provider"), key_info_manager: "sqlite-manager", library_path: "/usr/local/lib/softhsm/libsofthsm2.so", slot_number: None, serial_number: None, user_pin: None, software_public_operations: None, allow_export: None }) chosen in the configuration was not compiled in Parsec binary.
Error: provider not compiled

Also minor issue, parsec tool does not read the config.toml file by default,

Error: Failed to read config file from path: config.toml```
@gowthamsk-arm
Copy link
Contributor

gowthamsk-arm commented Sep 2, 2024

The parsec service in quickstart package is compiled only for mbedcrypto provider as seen here
https://github.com/parallaxsecond/parsec/blob/main/quickstart/quickstart.Dockerfile#L35

This is intentionally done. For rest of the providers, you can compile the main branch and configure the service.

As for the parsec-tool, can you point me to the command in the parsec-book that you are trying to run? :)

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

No branches or pull requests

2 participants