We have the same problem with CentOS and old openssh. I found a new version [1] the other day and plan on trying it out, but haven't had the chance yet. It is from the CentOS CR (continuous release) repo [2].
[1] - http://lists.centos.org/pipermail/centos -cr-announce/2013-November/001033.html [2] - http://wiki.centos.org/AdditionalResources/Repositories/CR On Wed, Jan 15, 2014 at 11:00 AM, Stan Lemon <[email protected]> wrote: > This is sort of picking up on an exchange I started with Michael on > twitter. > > I read http://blog.ansibleworks.com/author/michaeldehaan/ and was curious > about the paramiko piece, specifically if this could be circumvented by > finding a repo that would server up a newer version of the ssh client for > me. > > I'm also just curious in general what is recommended for using ansible > both on the host and destination side. I find myself using the latest > CentOS6 a lot, but wonder if there's a better route I should be looking at > to ensure speed and efficiency when be managed by ansible. > > Thanks, > > - Stan Lemon > [email protected] > > -- > 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. > -- Peter Gehres Site Reliability Engineer | AppDynamics, Inc. www.appdynamics.com | AS62897 -- 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.
