# pycrypto2.6, paramiko, Ansible 1.6 issue

**URL:** <https://forum.ansible.com/t/pycrypto2-6-paramiko-ansible-1-6-issue/15123>\
**Category:** Ansible Project\
**Created:** [April 30, 2014, 5:26pm UTC](https://forum.ansible.com/t/pycrypto2-6-paramiko-ansible-1-6-issue/15123 "2014-04-30T17:26:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark\_Phillips](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@Mark\_Phillips](https://forum.ansible.com/u/Mark_Phillips)\
**Post date:** [April 30, 2014, 5:26pm UTC](https://forum.ansible.com/t/pycrypto2-6-paramiko-ansible-1-6-issue/15123/1 "2014-04-30T17:26:22Z")

</div>

Folks,

I’m running CentOS6.5, and have pulled the default python-crypto RPM to use a newer version so Vault works. I’m running an RPM build from the Ansible source (devel branch - ansible-1.6-0.git201404301338.el6.noarch)

The EPEL python-crypto2.6 RPM seems to have the Crypto directory under the egg dir when installed:

[root@host pycrypto-2.6.1-py2.6-linux-x86\_64.egg]# ls -ld Crypto/

drwxr-xr-x. 10 root root 4096 Apr 30 17:10 Crypto/

… which then means paramiko doesn’t find it, and, well, long story short, nothing works.

I do realise this isn’t particularly an Ansible problem, but I’m wondering if anybody else is experiencing the same problem on a CentOS 6 host with a recent Ansible. Is it a Python/library path issue?

Cheers,

–Mark