On Thu, 19 Dec 2013 13:46:15 -0400
Joey Hess <[email protected]> wrote:
> CrabMan wrote:
> > Here I attach a screenshot of mentioned window. Also I think the name of
> > the process is ssh-askpass.
>
> So, this is not a password prompt at all, which explains a lot.
> Looks like it expected one host at an address, and got another one.
>
> Hmm, one scenario would be, if you locally paired on your home network,
> and went to work (for example), there might be a computer at work with
> the same address. If it also has ssh, this would happen.
>
> Can you post the relevant part of your ~/annex/.git/config for this
> remote? I'm particularly curious if it decided it had to hardcode the IP
> address, which would make this kind of collision more likely than if it
> had been able to use the LAN's DNS, or mDNS for the remote.
>
> I think I can fix this easily by making git-annex always use
> StrictHostKeyChecking, both when transferring to remotes, and when
> syncing.
>
> --
> see shy jo
[remote "192.168.1.2_annex"]
url = ssh://[email protected]_annex/~/annex/
fetch = +refs/heads/*:refs/remotes/192.168.1.2_annex/*
annex-cost = 175.0
----
CrabMan <[email protected]>
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
