Re: SSH-2.0-OpenSSH_3.4p1 and SSH-2.0-OpenSSH_3.7.1p2 : StrictHostKeyChecking
- From: Darren Tucker <dtucker@xxxxxxxxxxxxxxxx>
- Date: 31 Jan 2006 07:13:41 GMT
On 2006-01-31, gnitin21@xxxxxxxxx <gnitin21@xxxxxxxxx> wrote:
> That make sense. Thanks for clarification.
>
> Are the ssh config file formats are standardized ? i mean what
> parameter and their values ! [later ref
[...]
> i checked this site "www.ietf.org/html.charters/secsh-charter.html "
> but could not see any reference for ssh configuration.
No, the only file format (that I know of) that is part of the standard is
the public key file format, and that was relatively late in the process.
For OpenSSH, the config file format is documented in the ssh_config(5)
man page (and sshd_config(5) for the corresponding server config file).
> is it left to the implementators to include what is needed an what
> notation !!
Yes.
--
Darren Tucker (dtucker at zip.com.au)
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69
Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.
.
- References:
- Prev by Date: Re: SSH-2.0-OpenSSH_3.4p1 and SSH-2.0-OpenSSH_3.7.1p2 : StrictHostKeyChecking
- Next by Date: rdist question
- Previous by thread: Re: SSH-2.0-OpenSSH_3.4p1 and SSH-2.0-OpenSSH_3.7.1p2 : StrictHostKeyChecking
- Next by thread: AllowUsers doesn't work with IPs
- Index(es):
Relevant Pages
|
|