-
Notifications
You must be signed in to change notification settings - Fork 15
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
Paths for .so file are wrong on Ubuntu #6
Comments
|
Other than the issues I reported, I was able to successfully work through the Howto on Ubuntu 19.10! Thanks a lot for posting this. The other Howto that involved GPG was so complex that I eventually gave up. Even if I got it to work, it wasn't something that I could recommend to co-workers and it seemed like to break over time. This is simpler! |
|
That is an interesting issue. Is the For dpkg-based systems you can use Glad you found the found the guide useful otherwise! |
|
The ssh-agent integration was the one piece I didn't test last night. I'll test that tonight. |
|
On Ubuntu 18.04, I can programmatically find the right path to the .so file like this: |
|
I tested the agent integration on Ubuntu 18.04 and it worked. I used The "whitelisted paths" concern you raised will not be a problem. According to |
|
I don't use Ubuntu anymore and it looks the |
The correct path for the .so file on Ubuntu varies depending on the architecture. A complete list of the file paths used is here:
https://packages.ubuntu.com/search?searchon=contents&keywords=opensc-pkcs11.so+&mode=exactfilename&suite=eoan&arch=any
The most common one used would be:
I'm not sure how you want to handle this in the documentation. Maybe in one step instruct users to export a shell variable with the right path, and then refer to the variable in the remaining shell commands. That would keep most the commands as "copy/pasteable" for most users.
The text was updated successfully, but these errors were encountered: