On 2013-03-25 02:53, Holger Parplies wrote:
> actually, don't. StrictHostKeyChecking is on by default for a good reason.
> Without it, you're vulnerable to MITM attacks,
Which in the case of SSH key authentication, means only that the data
crossing the SSH tunnel could be read. While that's bad, e
Hi,
[for the archives]
Tyler J. Wagner wrote on 2012-12-11 11:08:17 + [Re: [BackupPC-users] Thank
you BackupPC!!!]:
> [...]
> Consider:
>
> root@venkman:~# cat /var/lib/backuppc/.ssh/config
> Protocol 2
> HashKnownHosts no
> StrictHostKeyChecking no
actually, don
On 2012-12-11 03:39, Richard Shaw wrote:
> Well after getting the system up I went in and logged in as the
> backuppc user, killed the IP from known_hosts (since it generated a
> new rsa key on install) and did a ssh-copy-id (much easier then doing
> the key exchange by hand) an voila!
Consider:
Just a shameless plug here...
I was "upgrading" my old Fedora 14 MythTV box to CentOS 6.3 which
didn't go so well on the MythTV front, but that's another story. Well
when that didn't work I decided to go with Fedora 17.
In both cases I have a /var lvm partition but since all my pictures,
movies,
