From d2eb89453922b46db916cd596f972efd5d9062d4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?D=C3=A1vid=20N=C3=A9meth?= Date: Tue, 9 Apr 2024 13:48:53 +0200 Subject: [PATCH] feat: update the paramiko description --- docs/docsite/rst/reference_appendices/glossary.rst | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/docsite/rst/reference_appendices/glossary.rst b/docs/docsite/rst/reference_appendices/glossary.rst index ce35c16e47..8419834ae1 100644 --- a/docs/docsite/rst/reference_appendices/glossary.rst +++ b/docs/docsite/rst/reference_appendices/glossary.rst @@ -354,12 +354,11 @@ when a term comes up on the mailing list. Ansible orchestration is all about modeling that kind of process. paramiko - By default, Ansible manages machines over SSH. The library that - Ansible uses by default to do this is a Python-powered library called - paramiko. The paramiko library is generally fast and easy to manage, - though users who want to use Kerberos or Jump Hosts may wish to switch - to a native SSH binary such as OpenSSH by specifying the connection - type in their :term:`playbooks`, or using the ``-c ssh`` flag. + By default, Ansible uses native OpenSSH, because it supports ControlPersist. + If your control machine uses an older version of OpenSSH that does not support ControlPersist, + Ansible will fall back to a Python implementation of OpenSSH called 'paramiko'. + The paramiko library is generally fast and easy to manage. To use paramiko + you need to specify the connection type in your :term:`playbooks`, or by using the ``-c paramiko`` flag. Playbooks Playbooks are the language by which Ansible orchestrates, configures,