Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1820150

Summary:	crypto_kdf_derive_from_key segfaults on ARM
Product:	[Fedora] Fedora	Reporter:	Petr Viktorin <pviktori>
Component:	python-libnacl	Assignee:	Jonny Heggheim <hegjon>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	33	CC:	hegjon, sergio
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-libnacl-1.7.2-3.fc34	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-11 01:02:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	245418

Description Petr Viktorin 2020-04-02 11:33:50 UTC

On the ARM architecture, crypto_kdf_derive_from_key segfaults due to not declaring argument types in ctypes. Specifically, ctypes defaults to `int` for `subkey_id` but the C library expects `uint64_t`.
I posted more info upstream: https://github.com/saltstack/libnacl/issues/123

On other architectures, the bug manifests as not being able to use larger subkey IDs: https://github.com/saltstack/libnacl/issues/122

A call to the function is part of the tests, making python-libnacl FTBS on ARM builders.

Comment 1 Ben Cotton 2020-08-11 13:16:20 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle.
Changing version to 33.

Comment 2 Sergio Basto 2020-08-12 20:32:15 UTC

Thank you to pointing out that is a ARM problem , I could built it on other arch .

Comment 3 Sergio Basto 2021-05-07 09:20:12 UTC

applied https://src.fedoraproject.org/rpms/python-libnacl/blob/rawhide/f/libacl_issue_126.patch

Comment 4 Fedora Update System 2021-07-02 05:00:09 UTC

FEDORA-2021-23692092b3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-23692092b3

Comment 5 Fedora Update System 2021-07-03 01:04:26 UTC

FEDORA-2021-23692092b3 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-23692092b3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-23692092b3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-07-10 22:03:40 UTC

FEDORA-2021-a314f6cb2f has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-a314f6cb2f

Comment 7 Fedora Update System 2021-07-11 01:02:55 UTC

FEDORA-2021-23692092b3 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2021-07-11 01:22:07 UTC

FEDORA-2021-a314f6cb2f has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-a314f6cb2f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-a314f6cb2f

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.