Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
In RHEL7 a new -n option had been added:
   -n name,... User/host principal names to include in certificate

In previous RHELs we had a downstream patch that made it possible to use NSS db for storing the public keys:
   -n      Extract the public key from smartcard.

Also the whole NSS patch is missing

Version-Release number of selected component (if applicable):
openssh-6.1p1-4.el7

How reproducible:
100%

Steps to Reproduce:
1. man openssh
2. try to use ssh-keygen with -n
3. try to use UseNSS with sshd
  
Actual results:
Conflict and no NSS patch applied

Expected results:
Well, I do not know? What does the developer think?

Additional info:

There is no NSS support in the openssh-6.1p1-4.el7, It's not needed anymore since there is a direct smartcards support using PKCS#11 library in openssh, ssh-keygen -D, ssh -I and others

Ok thanks, I will try to update the test to cover the direct support.