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

Certificate subjectdn and nickname parameters #1747

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

Certificate subjectdn and nickname parameters #1747

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 #1184. Originally filed by saipandi on 2014-10-15 17:37:57:

  • Assigned to nobody

For the CA installer tests I tested, giving the same subjectdn for two certificates, the same nickname for two certificates and an empty nickname for a certficate.

When I give the same subjectdn or nickname for two certs, the installation fails but "Installation Failed" is the only error I get, there should be a more descriptive error. A check should be kept for the subjectdns and nicknames to verify their uniqueness.

Also, if we give an empty nickname on the other hand, a NULL certificate gets created and the installatoion goes through fine but on executing the pk12util command we get a segmentation fault. So a check should be kept for the empty nickname provided by the user and if that is the case, then the default nickname can be taken or an error message can be given.

@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 saipandi at 2014-10-15 21:32:07

Also, while checking for invalid key sizes for a certificate I get a non-descriptive "Installation Failed" error. A check for valid key sizes should be kept.

@pki-bot
Copy link
Author

pki-bot commented Oct 3, 2020

Comment from saipandi at 2017-02-27 14:03:03

Metadata Update from @saipandi:

  • 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