# Running Ansible from source on Linux with F-Secure SSH instead of OpenSSH; only user privileges **URL:** \ **Category:** Ansible Project\ **Created:** [November 25, 2014, 3:11pm UTC](https://forum.ansible.com/t/running-ansible-from-source-on-linux-with-f-secure-ssh-instead-of-openssh-only-user-privileges/16877 "2014-11-25T15:11:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Ed\_Voncken](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@Ed\_Voncken](https://forum.ansible.com/u/Ed_Voncken)\ **Post date:** [November 25, 2014, 3:11pm UTC](https://forum.ansible.com/t/running-ansible-from-source-on-linux-with-f-secure-ssh-instead-of-openssh-only-user-privileges/16877/1 "2014-11-25T15:11:42Z")
Hi, Started discussing this on Twitter with a.o. @laserllama. I’m facing a nice (\*) challenge: - As a regular user (no special sudo / root privileges), - I need to run Ansible from source - on a Linux which has /usr/bin/python == Python 2.6.8 - with F-Secure SSH instead of OpenSSH \*) For small values of ‘nice’ I’m encountering the following issues so far: 1. Ansible source seems to hard code “/usr/bin/python” (2.6.8). I decided to go the “virtualenv” route, so I can at least install required Python modules in a specific ‘ansible’ virtualenv. I’m still fighting PIP’s refusal to talk through our SSL proxy. (ansible)$ pip --version pip 1.5.6 from /opt/local/python/ansible/lib/python2.6/site-packages (python 2.6) I have other virtualenv’s based on more recent (non-OS supplied) Python 2.7.2, and they don’t appear to have this issue. 1. Lots of OpenSSH-specific options are hard coded in ssh.py F-Secure SSH is a completely different beast from OpenSSH; completely different set of options. I’ve hacked around in ssh.py a bit, and progressed somewhat. Any advice on the best way forward? - Is there a proper way to use another Python when running Ansible from source? - Anyone have experience getting Ansible to work with other SSH than OpenSSH? Thanks, Ed. ---
**Author:** ![Vincent\_Van\_der\_Kuss](https://avatars.discourse-cdn.com/v4/letter/v/7c8e57/32.png) [@Vincent\_Van\_der\_Kuss](https://forum.ansible.com/u/Vincent_Van_der_Kuss)\ **Post date:** [November 25, 2014, 7:11pm UTC](https://forum.ansible.com/t/running-ansible-from-source-on-linux-with-f-secure-ssh-instead-of-openssh-only-user-privileges/16877/2 "2014-11-25T19:11:40Z")
> Hi, > > Started discussing this on Twitter with a.o. @laserllama. I'm facing a nice > (\*) challenge: > > - As a regular user (no special sudo / root privileges), > - I need to run Ansible from source > - on a Linux which has /usr/bin/python == Python 2.6.8 > - with F-Secure SSH instead of OpenSSH > > \*) For small values of 'nice' > > I'm encountering the following issues so far: > > 1) Ansible source seems to hard code "/usr/bin/python" (2.6.8). > > I decided to go the "virtualenv" route, so I can at least install required > Python modules in a specific 'ansible' virtualenv. > I'm still fighting PIP's refusal to talk through our SSL proxy. >   (ansible)$ pip --version >   pip 1.5.6 from /opt/local/python/ansible/lib/python2.6/site-packages > (python 2.6) Which operating system? I had to update setuptools to 1.0.1 on CentOS7 to get pip working over a proxy. ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [November 25, 2014, 10:26pm UTC](https://forum.ansible.com/t/running-ansible-from-source-on-linux-with-f-secure-ssh-instead-of-openssh-only-user-privileges/16877/3 "2014-11-25T22:26:09Z")
for fsecure you might need a new connection plugin if it is that different than the ssh one. Have you tried with paramiko? ---
**Author:** ![Ed\_Voncken](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@Ed\_Voncken](https://forum.ansible.com/u/Ed_Voncken)\ **Post date:** [November 27, 2014, 10:12pm UTC](https://forum.ansible.com/t/running-ansible-from-source-on-linux-with-f-secure-ssh-instead-of-openssh-only-user-privileges/16877/4 "2014-11-27T22:12:08Z")
Hi Vincent, > Which operating system? I had to update setuptools to 1.0.1 on CentOS7 > to get pip working over a proxy. It’s SLES10 update 3; I suspect that it’s the ancient Python version that’s biting me. Due to other fires, I haven’t made much progress. Perhaps next week 😉 ---
**Author:** ![Ed\_Voncken](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@Ed\_Voncken](https://forum.ansible.com/u/Ed_Voncken)\ **Post date:** [November 27, 2014, 10:13pm UTC](https://forum.ansible.com/t/running-ansible-from-source-on-linux-with-f-secure-ssh-instead-of-openssh-only-user-privileges/16877/5 "2014-11-27T22:13:01Z")
Hi Brian, > for fsecure you might need a new connection plugin if it is that > different than the ssh one. Have you tried with paramiko? Nope, haven’t tried Paramiko - will look into that, thanks. ---
**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\ **Post date:** [December 1, 2014, 9:18pm UTC](https://forum.ansible.com/t/running-ansible-from-source-on-linux-with-f-secure-ssh-instead-of-openssh-only-user-privileges/16877/6 "2014-12-01T21:18:46Z")
“1) Ansible source seems to hard code “/usr/bin/python” (2.6.8).” See the docs regarding ansible\_python\_interpreter for remote interpreters, elsewhere it will use whatever Python is in your path.