#2910 pkispawn fails to mask specified parameter values under the [DEFAULT] section
Closed: fixed 7 years ago Opened 7 years ago by mharmsen.

It appears that parameter values under the [DEFAULT] section in the /etc/pki/default.cfg file are failing to be masked (unlike specified parameter values under all of the other sections of this file).


Metadata Update from @mharmsen:
- Custom field component adjusted to None
- Custom field feature adjusted to None
- Custom field origin adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1532759
- Custom field type adjusted to None
- Custom field version adjusted to None

7 years ago

master:

commit 26bc698847b5348033ce3abb225ed24ebce4386d (origin/master, origin/HEAD, gerrit/master, master)
Author: Ade Lee alee@redhat.com
Date: Tue Jan 9 12:14:23 2018 -0500

Fix masking in the archived deployment.cfg

Resolves rhbz#1532759
Change-Id: Ia464852bab792b1629436ddbb963be1479579bc4

10.5:

commit 70ef976dfabe2c34ed69ac00c8868b3c7f6d825b (HEAD -> masking_fix_10.5)
Author: Ade Lee alee@redhat.com
Date: Tue Jan 9 12:14:23 2018 -0500

Fix masking in the archived deployment.cfg

Cherry-picked from 26bc698847b5348033ce3abb225ed24ebce4386d
Resolves rhbz#1532759
Change-Id: Ia464852bab792b1629436ddbb963be1479579bc4

Metadata Update from @vakwetu:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

7 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.4 (was: 10.5)

7 years ago

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.5.4-1.fc27

7 years ago

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/3028

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Log in to comment on this ticket.

Metadata