Red Hat Bugzilla – Bug 1020432
Fix man page for ssh-keygen because of certificate support
Last modified: 2013-11-21 17:59:33 EST
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):
Steps to Reproduce:
1. man ssh-keygen, check -n and -Z documentation
no -Z documentation
Properly documented -Z option for passing principal list
Created attachment 813656 [details]
diff --git a/ssh-keygen.1 b/ssh-keygen.1
index fa520d4..8dfa302 100644
@@ -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:
-.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"
Additional limitations on the validity and use of user certificates may
be specified through certificate options.
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.