pkispawn CA with HSM and RHEL 7.4 in FIPS mode fails.
Steps to Reproduce:
1. RHEL 7.4 server system is in FIPS mode and has the latest available selinux-policy-3.13.1-148.el7.noarch 2. Selinux is set to permissive due to https://bugzilla.redhat.com/show_bug.cgi?id=1447436#c5 3. pkispawn CA with HSM.
Actual results:
see associated bug
Expected results:
pkispawn should be successful.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1450143 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue assigned to jmagne - Issue priority set to: critical
The following patch was tested and checked-in:
commit ee5af05036e87a9dad821c9dd8bc0198dac9bd65 Author: Matthew Harmsen mharmsen@redhat.com Date: Fri May 12 13:00:54 2017 -0600
Fix CA installation with HSM in FIPS mode Bugzilla Bug #1450143 - CA installation with HSM in FIPS mode fails dogtagpki Pagure Issue #2684 - CA installation with HSM in FIPS mode fails
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.5 (was: 10.4) - Issue status updated to: Closed (was: Open)
commit 641180a465d7fdf12a978c9c458e39bf6829cac2 Author: Matthew Harmsen mharmsen@redhat.com Date: Tue May 16 12:58:17 2017 -0600
Added FIPS class to pkispawn Bugzilla Bug #1450143 - CA installation with HSM in FIPS mode fails dogtagpki Pagure Issue #2684 - CA installation with HSM in FIPS mode fails
commit 4f11d3b2aad075c965bbccb61112d443e36e4c45 Author: Matthew Harmsen mharmsen@redhat.com Date: Mon May 15 15:06:04 2017 -0600
Added runtime requirement on sysctl to pki-core spec file
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.7-1.fc27
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2804
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Log in to comment on this ticket.