Bug 116879

Summary: [patch] ssh-keygen not clear whether authorized_keys is file or dir
Product: Documentation Reporter: Warren Block <wblock>
Component: Books & ArticlesAssignee: Daniel Gerzo <danger>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
file.diff none

Description Warren Block 2007-10-03 20:50:01 UTC 
The Handbook OpenSSH/ssh-keygen section says

"The public key must be placed in ~/.ssh/authorized_keys of the remote machine in order for the setup to work. Similarly, RSA version 1 public keys should be placed in ~/.ssh/authorized_keys."

The usage of "in" is ambiguous, and can be read as "place the key file in a directory called authorized_keys".

Fix: Apply the attached patch.

Patch attached with submission follows:
How-To-Repeat: Read the OpenSSH/ssh-keygen section of the Handbook.
Comment 1 Daniel Gerzo freebsd_committer freebsd_triage 2007-10-03 21:05:54 UTC 
Responsible Changed
From-To: freebsd-doc->danger

Take
Comment 2 dfilter service freebsd_committer freebsd_triage 2007-10-03 21:35:43 UTC 
danger      2007-10-03 20:35:35 UTC

  FreeBSD doc repository

  Modified files:
    en_US.ISO8859-1/books/handbook/security chapter.sgml 
  Log:
  - Add <acronym> tags around RSA and DSA words,
  - ensure reader that the ~/.ssh/authorized_files is pure file and not
    directory [1],
  - simplify the last part of para,
  - 8 spaces = tab, while here.
  
  PR: docs/116879 [1]
  
  Revision  Changes    Path
  1.315     +7 -6      doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml
_______________________________________________
cvs-all@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org"
Comment 3 Daniel Gerzo freebsd_committer freebsd_triage 2007-10-03 21:35:57 UTC 
State Changed
From-To: open->closed

Fixed in rev. 1.315. (I have committed a bit modified patch than the one 
you have submitted.) 

New version should be on-line in a few hours after next scheduled 
documentation rebuild. 
Thanks for your submission!