-
Notifications
You must be signed in to change notification settings - Fork 13
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
[0.1.1] Seg fault in test suite #37
Comments
Thanks @remicollet for the feedback. Please, which Linux version are are you using ? I guess fc33, doesn't it ?
Can you run the same test using the upstream SoftHSM2 ? thank you, |
I'll try to reproduce this this week |
Yes, Fedora 33 Using softhsm-2.6.1 |
I don't get the same result when testing myself on Fedora 33. I am getting a lot of skipped tests, but no error. An interesting piece though is this:
It looks like the softhsm package itself is having trouble. |
It turns out that after restarting the VM, I'm able to reproduce the issue. I will investigate further. |
I managed to run all tests successfully by simply setting
|
@remicollet I get no error with compiling SoftHSM 2.6.1 from source rather than using the one provided by the fedora package. There seems to be a problem in the fedora provided package, not in this extension. If we can find indications to the contrary, I'll reopen, but in the meantime, I'm closing this. |
That's probably mean that this is related to security enhancement build options used by default for RPM build |
@remicollet Please, can you provide some inside about some specific security build options that are used ? Should we apply the same to the build of php-pkcs11 extension ? |
At least Also
Some may make sense. |
P.S. due to some familly event I have very minimal activity, at least for next week. |
@remicollet, in the issue on SoftHSM, they suggested a fix, which I wasn't able to test properly, since compiling it vanilla worked just fine, so there was no effective difference. Are you able to build it with those options you mentioned and confirm whether they trigger the issue, and then try their fix ? |
Moved to issue #51. Not sure if this is relevant, but when doing something like this (pseudo code):
Before the Update: |
Was able to find time to run some tests
So, looks like some recent changes in master fix this issue. |
Thanks Rémi for the follow up. |
:) @vjardin simply "Remi", without accent ;) |
Sorry for the late reply, but thanks Remi for taking the time on this. |
@gamringer is a new release plan soon ? |
Yes. I want to figure out #53 before make another release, but it will be the last item. |
I confirm version 1.0 is OK, build and test suite passes on Fedora 32 to 34, RHEL 7 and 8 |
thanks @remicollet for the feedbacks. |
Awesome, thanks
…On Wed., Mar. 24, 2021, 02:15 Remi Collet, ***@***.***> wrote:
I confirm version 1.0 is OK, build and test suite passes on Fedora 32 to
34, RHEL 7 and 8
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA64NL5CGFQB2Z7M3WPEBZ3TFF7PNANCNFSM4V4GSDEQ>
.
|
Sefault during 3 tests
Encrypt/Decrypt using AES-GCM [tests/0141-sym-encrypt-aes-gcm.phpt]
Encrypt/Decrypt using AES-GCM with update [tests/0145-sym-encrypt-aes-gcm-update.phpt]
Wrapping/Unrapping using RSA OAEP [tests/0165-rsa-encrypt-oaep-wrap.phpt]
Example:
The text was updated successfully, but these errors were encountered: