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

Configuration directives rely on absolute paths #7

Open
nmav opened this issue Mar 10, 2015 · 1 comment
Open

Configuration directives rely on absolute paths #7

nmav opened this issue Mar 10, 2015 · 1 comment

Comments

@nmav
Copy link

nmav commented Mar 10, 2015

The configuration directives for example in filter.conf rely on absolute paths to obtain the used library. That means that configuration files cannot be shared by multiple platforms, and more importantly multi-arch distributions cannot possibly use it. For example the softhsm library may be available on the following two different paths depending on the architecture:
modules = [("softhsm", "/usr/lib64/pkcs11/libsofthsm.so")]
modules = [("softhsm", "/usr/lib/pkcs11/libsofthsm.so")]

I think the best would be to use the --libdir configure option and then allow relative library paths over that. That way there can be a 32-bit pkcs11proxyd and 64-bit pkcs11proxyd installed in the same system and share the same configuration file.

@tc-anssi
Copy link
Contributor

Indeed, I will investigate and check if OCamlnet Netplex configuration parser can use relative paths (last time I check it did not).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants