Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 25 Jul 2006 09:25:07 -0600 (MDT)
From:      Warren Block <wblock@wonkity.com>
To:        Alan Amesbury <amesbury@umn.edu>
Cc:        freebsd-doc@freebsd.org, FreeBSD-gnats-submit@freebsd.org
Subject:   Re: docs/100795: Typo in ssh_config(5)
Message-ID:  <20060725091815.B1882@wonkity.com>
In-Reply-To: <20060725015510.C21E445065@paulaner.oitsec.umn.edu>
References:  <20060725015510.C21E445065@paulaner.oitsec.umn.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 24 Jul 2006, Alan Amesbury wrote:

>> Fix:
> Apply this patch to ssh_config.5:
>
> *** ssh_config.5.orig   Mon Jul 24 20:50:13 2006
> --- ssh_config.5        Mon Jul 24 20:50:20 2006
> ***************
> *** 461,467 ****
>  be disclosed.
>  The default is
>  .Dq no .
> ! Note that hashing of names and addresses will not be retrospectively applied
>  to existing known hosts files, but these may be manually hashed using
>  .Xr ssh-keygen 1 .
>  .It Cm HostbasedAuthentication
> --- 461,467 ----
>  be disclosed.
>  The default is
>  .Dq no .
> ! Note that hashing of names and addresses will not be retroactively applied
>  to existing known hosts files, but these may be manually hashed using
>  .Xr ssh-keygen 1 .
>  .It Cm HostbasedAuthentication
>
> In that context, "retrospectively" makes less sense than "retroactively."

Agreed, but that whole sentence is confusing.  How about this:

! Note that unhashed names and addresses already in known hosts files
   will not be hashed automatically, but these may be manually hashed
   using
   .Xr ssh-keygen 1 .

-Warren Block * Rapid City, South Dakota USA



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060725091815.B1882>