That was a stack overflow post I created, I’ve been trying to figure out for 
the last 3 weeks why I couldn’t check out a project (R/W) from github using 
Ansible.

Finally, I started taking Vagrant apart to figure out how it’s ssh behaviour 
differed from Ansible’s, that was where I got to. 

Give it a go yourself, I don’t know why it is, but it’s the observable 
behaviour using the default SSH provided with OSX Mavericks.




On 8 Jan 2014, at 17:11, Michael DeHaan <[email protected]> wrote:

> That seems curious. 
> 
> Is anyone else observing this behavior and do we have any documentation more 
> reliable than Stack Overflow, such as an upstream bug report or mailing list 
> thread to reference?
> 
> I hesitate making such changes based on observed stack overflow posts, and 
> suspect there's a tradeoff to switching, but that's me just wanting to show 
> extra caution on my part.
> 
> (It's also not ssh_alt specific so it shouldn't block forward progress on 
> this front)
> 
> 
> 
> 
> 
> 
> 
> 
> On Wed, Jan 8, 2014 at 11:06 AM, bryan hunt <[email protected]> wrote:
> I've been doing a lot of research on why I couldn't get ssh forwarding to 
> work with Ansible. 
> 
> I think I've found a bug (in ssh) regarding how it performs authentication, 
> the behavior varies depending on how you express the command line arguments.
> 
> http://stackoverflow.com/questions/20952689/vagrant-ssh-agent-forwarding-how-is-it-working?noredirect=1#comment31511341_20952689
> 
> In a nutshell . if you execute SSH like so:
> 
> ssh -o HostName=127.0.0.1 -o User=vagrant -o.........
> 
> SSH Agent forwarding doesn't work, regardless of how you specify the 
> remaining options. 
> 
> But if you execute it like so, it does: 
> 
> ssh [email protected] -o ..........
> 
> It would be awesome if it executed the SSH command in that manner.
> 
> 
> On Saturday, January 4, 2014 7:01:55 PM UTC, Michael DeHaan wrote:
> The "ssh_alt" connection type as implemented by Jerome Wagner greatly reduces 
> the amount of operations performed over connections by not transferring 
> modules as files for many cases.  It's pretty impressive.
> 
> It can currently be tested on the development branch with "connection: 
> ssh_alt" in a play, or "-c ssh_alt".
> 
> I would like this to become the default in Ansible devel, to be released as 
> the default in 1.5, in the next week or two.
> 
> As such, if everyone using the SSH transport (aka anyone not running from 
> RHEL/CentOS/EPEL 
> and still using paramiko), as they normally use Ansible, this will be greatly 
> appreciated.
> 
> I just recently merged in some tweaks to sudo password detection.
> 
> If we can get it past encountering any problems, we'll remove the old ssh.py 
> and replace ssh_alt.py as ssh.py, and there will be no more connection named 
> "ssh_alt".
> 
> Thank you!
> 
> -- 
> Michael DeHaan <[email protected]>
> 
> CTO, AnsibleWorks, Inc.
> http://www.ansibleworks.com/
> 
> 
> -- 
> 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 [email protected].
> To post to this group, send email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 
> 
> -- 
> Michael DeHaan <[email protected]>
> CTO, AnsibleWorks, Inc.
> http://www.ansibleworks.com/
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Ansible Project" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/ansible-project/IeF5rd68xZE/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> [email protected].
> To post to this group, send email to [email protected].
> For more options, visit https://groups.google.com/groups/opt_out.

-- 
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 [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to