bash-completion doesn't work with ssh

[acoster]

Binary package hint: bash

When you press tab when typing the ssh command, it is either ignored (if you started have already typed something and you don't have a preceding space or an @), or you get |1| instead of any data at all.

Examples:
ssh <tab> becomes ssh |1|
ssh xxx@p stills the same, even if you have a host begining with p on your known_hosts list.
ssh xxx@<tab> becomes ssh xxx@|1|

[Aldous Peñaranda (dous)]

For: ssh<tab>, well, there are other commands that start with ssh...

 * ssh-add
 * ssh-agent
 * etc...

[acoster (acoster)]

That's not the point. I don't mean the built-in bash filename/command name completion, but the script that, among other things, parses your known hosts list _when_ you use ssh...

[Aldous Peñaranda (dous)]

Okay, got it. :)

I'm using Dapper and it's currently using the hosts file (/etc/hosts).

[Aldous Peñaranda (dous)]

I just remembered something...

I checked my ~/.ssh/known_hosts file and everything is "garbled". I think I read somewhere that you can't decrypt this new format (of course, I may be wrong). It would be difficult to include the functionality to parse this file if that is the case.

[Dennis Kaarsemaker (dennis)]

 status Rejected

ssh now by default has "HashKnownHosts yes" -- to disable that:

echo "HashKnownHosts no" >> ~/.ssh/config