In the CERTIFICATES section of ssh-keygen.1, be consistent about using "host_key" and "user_key" for the respective key types.
Index: ssh-keygen.1 =================================================================== RCS file: /cvs/src/usr.bin/ssh/ssh-keygen.1,v retrieving revision 1.126 diff -u -p -r1.126 ssh-keygen.1 --- ssh-keygen.1 3 Jul 2015 03:49:45 -0000 1.126 +++ ssh-keygen.1 19 Aug 2015 17:45:18 -0000 @@ -680,7 +680,7 @@ and identifying the CA key by providing to .Fl s : .Pp -.Dl $ ssh-keygen -s ca_key.pub -D libpkcs11.so -I key_id host_key.pub +.Dl $ ssh-keygen -s ca_key.pub -D libpkcs11.so -I key_id user_key.pub .Pp In all cases, .Ar key_id @@ -693,7 +693,7 @@ By default, generated certificates are v 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 -h -n host.domain host_key.pub" .Pp Additional limitations on the validity and use of user certificates may be specified through certificate options. -- Christian "naddy" Weisgerber na...@mips.inka.de
