re: fix in comment 20 This fails (attempts to execute /home/user/.ssh/known_hosts) in a scenario like the following:
# snippet of ~/.ssh/config # subnet of frequently-changing hosts we trust Host 192.168.1.* StrictHostKeyChecking no UserKnownHostsFile /dev/null # some long-living hosts (to allow scripted access) Host 192.168.1.1 UserKnownHostsFile /home/user/.ssh/known_hosts Host 192.168.1.2 UserKnownHostsFile /home/user/.ssh/known_hosts Host 192.168.1.3 UserKnownHostsFile /home/user/.ssh/known_hosts If you're reading this comment, here is a workaround which simply excludes the trusted hosts from the original rule: Host !192.168.1.1 !192.168.1.2 !192.168.1.3 192.168.1.* UserKnownHostsFile /dev/null The above workaround also seems to work with the original karmic bash_completion.d/ssh (1:1.0-3ubuntu2). In particular, before the workaround, I had multiple different UserKnownHostsFile overrides (each for a distinct Host entry). Those UserKnownHostsFile lines above were the only ones in the ~/.ssh/config file. If my comment is a manifestation of different bug from the one under discussion, then disregard it. -- regression for completing remote files/dirs over ssh https://bugs.launchpad.net/bugs/449349 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
