Skip to content
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

Redundant cacertnickname property in CS.cfg #2162

Open
pki-bot opened this issue Oct 3, 2020 · 2 comments
Open

Redundant cacertnickname property in CS.cfg #2162

pki-bot opened this issue Oct 3, 2020 · 2 comments
Milestone

Comments

@pki-bot
Copy link

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #1603. Originally filed by edewata (@edewata) on 2015-09-09 00:29:43:

  • Assigned to nobody

The cacertnickname property in CS.cfg has been deprecated and replaced with certnickname. However, both of these properties are used and sometimes inconsistently, which may cause an error.

For example, the updateConfig() in CASigningCert.java and OCSPSigningCert.java update the cacertnickname property without updating certnickname, but the SigningUnit.getNickname() reads the certnickname first if it exists, so it may not read the new cacertnickname value.

Proposed solution:

  • all references to cacertnickname should be removed or replaced with certnickname
  • an upgrade script should be added to rename cacertnickname to certnickname or remove cacertnickname if certnickname already exists.

Proposed milestone: 10.3

@pki-bot pki-bot added this to the UNTRIAGED milestone Oct 3, 2020
@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2015-09-14 20:54:45

Per CS/DS Meeting of 09/14/2015 - 10.3

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from edewata (@edewata) at 2017-02-27 13:59:33

Metadata Update from @edewata:

  • Issue set to the milestone: UNTRIAGED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant