# \[DEPRECATION WARNING\]: PARAMIKO\_LOOK\_FOR\_KEYS option

**URL:** <https://forum.ansible.com/t/deprecation-warning-paramiko-look-for-keys-option/44276>\
**Category:** Get Help\
**Tags:** paramiko, ee\
**Created:** [August 11, 2025, 7:25pm UTC](https://forum.ansible.com/t/deprecation-warning-paramiko-look-for-keys-option/44276 "2025-08-11T19:25:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MallocArray](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mallocarray/32/1655_2.png) [@MallocArray](https://forum.ansible.com/u/MallocArray)\
**Post date:** [August 11, 2025, 7:25pm UTC](https://forum.ansible.com/t/deprecation-warning-paramiko-look-for-keys-option/44276/1 "2025-08-11T19:25:24Z")

</div>

Ever since we upgraded our EE to Ansible 2.18 we always get a Deprecation warning, but I’m not finding any references to PARAMIKO\_LOOK\_FOR\_KEYS in our ansible.cfg that sits in the root of the project or in any playbooks.

I don’t want to disable all deprecation warnings, but is this legit or something that I’m missing for this particular one? I had assumed we were seeing it because something was set to use the deprecated feature, but is that a false assumption?

```auto
ansible --version
[DEPRECATION WARNING]: PARAMIKO_LOOK_FOR_KEYS option. Reason: This option was moved to the plugin itself Alternatives: Use the option from the plugin itself. This feature 
will be removed in version 2.20. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
ansible [core 2.18.7]
  config file = /runner/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/local/lib/python3.12/site-packages/ansible
  ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections:/runner/collections
  executable location = /usr/local/bin/ansible
  python version = 3.12.11 (main, Jun 4 2025, 00:00:00) [GCC 11.5.0 20240719 (Red Hat 11.5.0-7)] (/usr/bin/python3.12)
  jinja version = 3.1.6
  libyaml = True

```

---

<div class="post-metadata">

**Author:** ![shertel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shertel/32/1241_2.png) [@shertel](https://forum.ansible.com/u/shertel)\
**Post date:** [August 11, 2025, 9:59pm UTC](https://forum.ansible.com/t/deprecation-warning-paramiko-look-for-keys-option/44276/2 "2025-08-11T21:59:27Z")

</div>

PARAMIKO\_LOOK\_FOR\_KEYS is the name of an option that can be found in the config reference: [Ansible Configuration Settings — Ansible Community Documentation](https://docs.ansible.com/ansible/latest/reference_appendices/config.html#paramiko-look-for-keys).

I think the only way to avoid the deprecation warning (besides not use the option) would be to add additional configuration options to [ansible.builtin.paramiko\_ssh connection – Run tasks via Python SSH (paramiko) — Ansible Community Documentation](https://docs.ansible.com/ansible/latest/collections/ansible/builtin/paramiko_ssh_connection.html#parameter-look_for_keys) since they’re the same as the global (deprecated) options… But 2.18 is receiving only critical fixes at this point and the connection plugin itself is deprecated in 2.19.

You can run `ansible-config dump --only-changed` to see global configuration options (and append `-t all` to include all plugin configuration options).

---

<div class="post-metadata">

**Author:** ![MallocArray](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mallocarray/32/1655_2.png) [@MallocArray](https://forum.ansible.com/u/MallocArray)\
**Post date:** [August 12, 2025, 3:26pm UTC](https://forum.ansible.com/t/deprecation-warning-paramiko-look-for-keys-option/44276/3 "2025-08-12T15:26:31Z")

</div>

> [@shertel](#):
>
> ansible-config dump --only-changed

Thank you for the command. I look silly because this ultimately is in my ansible.cfg file, just slightly different.

I was searching my entire project for `PARAMIKO_LOOK_FOR_KEYS` which I didn’t find, but it was there as

```auto
[paramiko_connection]
look_for_keys = no

```

Removing that from my ansible.cfg removed the deprecation warning.

---

<div class="post-metadata">

**Author:** ![shertel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/shertel/32/1241_2.png) [@shertel](https://forum.ansible.com/u/shertel)\
**Post date:** [August 14, 2025, 2:28pm UTC](https://forum.ansible.com/t/deprecation-warning-paramiko-look-for-keys-option/44276/4 "2025-08-14T14:28:51Z")

</div>

I think the intention is the deprecation warning should occur if a plugin uses the global `PARAMIKO_LOOK_FOR_KEYS` setting (from ansible.constants or using the config manager). The paramiko connection plugin is not using it, so it’s a bug the deprecation warning occurs at all. I think this pull request would fix it: [optimize config for making it on demand and fix deprecation warnings by bcoca · Pull Request #74774 · ansible/ansible · GitHub](https://github.com/ansible/ansible/pull/74774).