# using no-pty authorized\_keys option with standard ssh transport

**URL:** <https://forum.ansible.com/t/using-no-pty-authorized-keys-option-with-standard-ssh-transport/17191>\
**Category:** Ansible Project\
**Created:** [January 5, 2015, 10:31pm UTC](https://forum.ansible.com/t/using-no-pty-authorized-keys-option-with-standard-ssh-transport/17191 "2015-01-05T22:31:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jeff\_Weber](https://avatars.discourse-cdn.com/v4/letter/j/9e8a1a/32.png) [@Jeff\_Weber](https://forum.ansible.com/u/Jeff_Weber)\
**Post date:** [January 5, 2015, 10:31pm UTC](https://forum.ansible.com/t/using-no-pty-authorized-keys-option-with-standard-ssh-transport/17191/1 "2015-01-05T22:31:29Z")

</div>

I’m using ansible to apply configuration on a few servers which have their ssh key configured with the “no-pty” option, and I’m attempting to work out the best configuration settings to use with ansible on them.

I can use the “paramiko” transport after enabling “pty=False” in the configuration file and all of my playbooks execute without issue.

The documentation indicates that pipeline mode isn’t allocating a pty, but not all tasks seem to run without asking for a pty. I see in the source for the ssh transport that there is an explicit passing of “-tt” in some cases (likely not ones covered by pipeline mode?), but I’ve not fully understood why.

Would it be possible to implement a similar flag to the pty=False for the normal ssh transport, or is there a reason to explicitly request a tty for some connections?

I’d like to be able to take advantage of the ssh transport (and pipeline mode) if possible, but obviously I can fall back to paramkio if there is no other option.