-
Notifications
You must be signed in to change notification settings - Fork 218
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
v3.3.2: p11tool --list-all does not see the available objects in token #241
Comments
Can you run ldd on the resulting libcryptoauth.so while on the target? |
The following YP recipe conf may help. Is the EXTRA_OECMAKE conf ok for v3.3.2?
|
I'm not able to replicate this failure. I'm seeing the expected behavior in ubuntu 20 LTS and Raspbian (Buster). The library should no longer throw errors when compiled with -fno-common per gcc 10 defaults so you should be able to remove the -fcommon flag. If you have p11-kit installed can you turn on call logging to see if it is able to open the library and successfully call the api? |
Do you mean setting "log-calls: yes" in /usr/share/p11-kit/modules/cryptoauthlib.module?
|
It looks like something is wrong with the built library. Can you dump the symbols? |
Try building with this patch applied:
|
NEED_USB is false, so your message is never hit. I've tried:
and I got:
|
|
Any other suggestions on how to tackle this? |
can you test a simple p11-kit list-modules -v???? |
@ambarus Disable the OpenSSL option in your build file - it serves no purpose in this configuration. |
@ambarus Okay stick with v3.2.5 or wait for v3.3.3 before updating the recipes. |
I disabled openssl, now p11tool sees the objects, but I get a segmentation fault:
|
Yes - #240 documents that. Because v3.3.3 is coming out next week that is why I suggest sticking with v3.2.5 or wait. |
Resolved in v3.3.3 |
Describe the bug
To Reproduce
Steps to reproduce the behavior:
linux4sam: ATECC608 (the one populated on sama5d27-wlsom1-ek) using cryptoauthlib v3.3.2.
Expected behavior
List available tokens.
Additional context
Same configuration but with cryptoauthlib v3.2.5, works just fine.
The text was updated successfully, but these errors were encountered: