Not the answer you're looking for, but why don't you just use ssh keys? It's some minor work upfront with huge security and automation benefits easier.
On Fri, Feb 13, 2015 at 3:51 PM, Ananda Debnath <ananda.debn...@gmail.com> wrote: > Does anyone know of an example to do this using password authentication? > > My inventory file has ansible_ssh_user and ansible_ssh_pass values set and > my ssh config file has password authentication set to yes. > > my.ssh.config > > Host 56.66.3.10 > User king > HostName 56.66.3.10 > ProxyCommand none > BatchMode yes > PasswordAuthentication yes > > # Also tried ssh -aY king@56.66.3.10 'nc -w 14400 %h %p' > Host * > ServerAliveInterval 60 > TCPKeepAlive yes > ProxyCommand ssh -AY king@56.66.3.10 'nc -w 14400 %h %p' > ControlMaster auto > ControlPath ~/.ssh/mux-%r@%h:%p > ControlPersist 15s > PasswordAuthentication yes > > But this isn't helping. I have a test role that applies to 56.66.3.10 first > and then other roles to the ones behind the bastion - redis-vm, etc. Neither > the bastion nor the vms behind it will let me through with passwords. > The ansible.cfg file looks like: > [defaults] > host_key_checking = False > # Tried both with and without this > transport=ssh > > [ssh_connection] > ssh_args = -F my.ssh.config > scp_if_ssh = True > control_path = ~/.ssh/mux-%%r@%%h:%%p > > The tail of the bastion login failure reads: > > debug2: key: /home/adebnath/.ssh/id_rsa ((nil)), > debug2: key: /home/adebnath/.ssh/id_dsa ((nil)), > debug2: key: /home/adebnath/.ssh/id_ecdsa ((nil)), > debug2: key: /home/adebnath/.ssh/id_ed25519 ((nil)), > debug1: Authentications that can continue: publickey,password > debug3: start over, passed a different list publickey,password > debug3: preferred > debug1: No more authentication methods to try. > Permission denied (publickey,password). > > > -- > 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 ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/c776ec2d-c640-4e2e-bb50-ecbd24548673%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- 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 ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAJQqANe2GHbaNvnpmaS8m%3D5xX6WFehWQ4ndfohvexcWsNvaO-g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
