On 28 Sep 1999, Niels Möller wrote:

[...]
> 
> Balazs Scheidler <[EMAIL PROTECTED]> writes:
> 
> > I'm trying to work on the publickey authorization database in lshd. I'd like
> > to ask for comments how to implement it.
> 
> It seems not entirely obvious how to get this right. Before commenting
> on publickey usereuthentication, let me say something about
> host authentication, which I feel is more urgent. More about user auth
> in my next mail.
> 
> When connecting, the client should look for a file
> .lsh/known_hosts/FQDN, where FQDN is the target host name provided by
> the user, preferably completed to a fully qualified domain name (I
Could the completion be optional?
I like the feature of ssh1 that host name to be taken from (or added to)
ssh_known_hosts or .ssh/known_hosts is exactly what I specify as host
name to ssh client. For hosts in the private network I use not DNS, just
/etc/hosts, and when I move a host to another location (so IP address is
changed), I just chenge /etc/hosts files on clients and need not touch
any ssh configuration files;
Also, I like the text format of ssh1 databases (because of stricter
licensing I do not use (and do not know) ssh2), and the freedom of
choosing tools I need (like vi, sed, etc).


> think it is possible to get adns to look up a host name using search
> directives in resolv.conf, and return both the ip-unmber and the
> FQDN).
>
[...]
> /Niels Möller
> 
Best regards,

Wojtek


Reply via email to