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.
Cause: "-n" option in ssh-keygen(1) program was renamed to "-Z" option, but ssh-keygen(1) manual page was not updated
Consequence: incorrect documentation
Fix: update ssh-keygen(1) manual page
Result: correct documentation
DescriptionMiroslav Vadkerti
2013-10-17 16:12:26 UTC
Description of problem:
Bug 906872 - certificate support in OpenSSH introduced a feature but the ssh-keygen man page was not adjusted correctly. The upstream provided -n option has been changed to -Z as the original is already used by our downstream patch. This needs to be properly documented in our version of man page. Without this our patch bring in an undocumented option and the usability of the feature becomes limited.
Version-Release number of selected component (if applicable):
openssh-5.3p1-94.el6
How reproducible:
100%
Steps to Reproduce:
1. man ssh-keygen, check -n and -Z documentation
Actual results:
no -Z documentation
Expected results:
Properly documented -Z option for passing principal list
Created attachment 813656[details]
fixed ssh-keygen.1
diff --git a/ssh-keygen.1 b/ssh-keygen.1
index fa520d4..8dfa302 100644
--- a/ssh-keygen.1
+++ b/ssh-keygen.1
@@ -113,7 +113,7 @@
.Fl s Ar ca_key
.Fl I Ar certificate_identity
.Op Fl h
-.Op Fl n Ar principals
+.Op Fl Z Ar principals
.Op Fl O Ar option
.Op Fl V Ar validity_interval
.Op Fl z Ar serial_number
@@ -300,7 +300,7 @@ candidate moduli for DH-GEX.
Extract the public key from smartcard.
.It Fl N Ar new_passphrase
Provides the new passphrase.
-.It Fl n Ar principals
+.It Fl Z Ar principals
Specify one or more principals (user or host names) to be included in
a certificate when signing a key.
Multiple principals may be specified, separated by commas.
@@ -549,8 +549,8 @@ names.
By default, generated certificates are valid for all users or hosts.
To generate a certificate for a specified set of principals:
.Pp
-.Dl $ ssh-keygen -s ca_key -I key_id -n user1,user2 user_key.pub
-.Dl "$ ssh-keygen -s ca_key -I key_id -h -n host.domain user_key.pub"
+.Dl $ ssh-keygen -s ca_key -I key_id -Z user1,user2 user_key.pub
+.Dl "$ ssh-keygen -s ca_key -I key_id -h -Z host.domain user_key.pub"
.Pp
Additional limitations on the validity and use of user certificates may
be specified through certificate options.
Comment 2RHEL Program Management
2013-10-24 08:08:05 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-1695.html