[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Pcompletion for ssh and scp
From: |
Manoj Srivastava |
Subject: |
Re: Pcompletion for ssh and scp |
Date: |
Wed, 05 Dec 2007 00:27:13 -0600 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.50 (gnu/linux) (x86_64-unknown-linux-gnu) |
On Tue, 04 Dec 2007 21:10:34 -0500, Stefan Monnier <address@hidden> said:
>> hostnames. It also assumes that each hostname is followed by either a
>> space or a comma, which is the case on the systems I've checked but
>> may not be a universal rule.
> All my known_hosts files have "hostnames" that are encoded in the
> following way:
1> bXOTR5GrVkVH4ABavbfZ7f2G0EQ=|drXHp56kwVXBTdc/f92649SXiTw=
> I don't know how widespread this is, but I haven't made anything
> special to get them: I'm using the standard Debian package without any
> special configuation in this respect, so for your feature to be useful
> I think it needs to handle this case.
If you do not want your hosts to be hashed, you need to add the
following lines to your ~/.ssh/config:
--8<---------------cut here---------------start------------->8---
Host *
HashKnownHosts no
--8<---------------cut here---------------end--------------->8---
I have found that various completion utilities (zsh has one as
well) work better if I do not have hashing turned on.
Since this is a user configurable option, perhaps it is OK for
pcompletion to work for people who have actively turned host hqshing
off, even if it does not handle hashed hosts?
manoj
--
Oh, I've seen copies [of Linux Journal] around the terminal room at The
Labs. Dennis Ritchie
Manoj Srivastava <address@hidden> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Re: Pcompletion for ssh and scp, Edward O'Connor, 2007/12/07