> i changed the permissions of my ssh config file with *chmod 600 ~/.ssh/config *but it didnt help. why would i get an ssh
Because an Ansible ping is really testing the (SSH) connection to the target machine.
>
> On Wed, Feb 3, 2021 at 1:48 PM Antony Stone <
Antony...@ansible.open.source.it
> <mailto:
Antony...@ansible.open.source.it>> wrote:
>
> On Wednesday 03 February 2021 at 19:21:03, Ken Cheng wrote:
>
> > i'm sorry if this was already covered but why does ansible's ping module
> > giving me an ssh error?
> >
> > i installed ansible version 2.9.17 on a centos vm. that vm can ping & ssh
> > to my test destination router from the command line. for some reason
> > "ansible lab -m ping" gives me an ssh error. my /etc/ansible/hosts file
> > looks ok (i just started with ansible this monday). what am i missing?
>
> Not to put too fine a point on it, I think what you are missing is reading the
> error message:
>
> > Permissions 0644 for '/home/xyz/.ssh/known_hosts' are too open.
> > It is required that your private key files are NOT accessible by others.
> > This private key will be ignored.
>
> So, change that mode 644 to 600 and all should be fine.
>
>
> Antony.
>
> --
> Numerous psychological studies over the years have demonstrated that the
> majority of people genuinely believe they are not like the majority of people.
>
> Please reply to the list;
> please *don't* CC me.
>
> You received this message because you are subscribed to the Google Groups "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
Debian and Sympa administration. Provisioning with Ansible.