1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
|
=============
Configuration
=============
Paramiko **does not itself** leverage `OpenSSH-style config file directives
<ssh_config>`_, but it **does** implement a parser for the format, which users
can honor themselves (and is used by higher-level libraries, such as
`Fabric`_).
The API for this is `.SSHConfig`, which loads SSH config files from disk,
file-like object, or string and exposes a "look up a hostname, get a dict of
applicable keywords/values back" functionality.
As with OpenSSH's own support, this dict will contain values from across the
parsed file, depending on the order in which keywords were encountered and how
specific or generic the ``Host`` or ``Match`` directives were.
.. note:;
Result keys are lowercased for consistency and ease of deduping, as the
overall parsing/matching is itself case-insensitive. Thus, a source file
containing e.g. ``ProxyCommand`` will result in lookup results like
``{"proxycommand": "shell command here"}``.
.. _ssh-config-support:
Keywords currently supported
============================
The following is an alphabetical list of which `ssh_config`_ directives
Paramiko directly supports (most of which involve the parsing/matching process
itself). It includes any departures from OpenSSH's implementation, which are
intentionally very few, and usually to support backwards compatibility with
Paramiko versions lacking some default parse-related behavior.
See `OpenSSH's own ssh_config docs <ssh_config>`_ for details on the overall
file format, and the intended meaning of the keywords and values; or check the
documentation for your Paramiko-using library of choice (e.g. `Fabric`_) to see
what it honors on its end.
- ``CanonicalDomains``: sets the domains used for hostname canonicalization.
- ``CanonicalizeFallbackLocal``: set to ``no`` to enforce that all looked-up
names must resolve under one of the ``CanonicalDomains`` - any names which
don't canonicalize will raise `CouldNotCanonicalize` (instead of silently
returning a config containing only global-level config values, as normal).
- ``CanonicalizeHostname``: as with OpenSSH, when a lookup results in this
being set to ``yes`` (whether globally or inside a specific block), it
triggers an attempt to resolve the requested hostname under one of the given
``CanonicalDomains``, which if successful will cause Paramiko to re-parse the
entire config file.
.. note::
As in OpenSSH, canonicalization is quietly ignored for "deep" hostnames -
by default, hostnames containing more than one period character. This may
be controlled with ``CanonicalizeMaxDots``; see below.
- ``CanonicalizeMaxDots``: controls how many period characters may appear in a
target hostname before canonicalization is disabled.
- ``AddressFamily``: used when looking up the local hostname for purposes of
expanding the ``%l``/``%L`` :ref:`tokens <TOKENS>`.
.. note::
As with the rest of these keywords, it does **not** apply to actual SSH
connections (as Paramiko's client classes do not load configs for you).
In fact, OpenSSH itself does not use this setting the way Paramiko does
(its lookup for ``%l`` does not appear to honor ``AddressFamily``).
- ``Host``: exact matching, full and partial globbing (``*``), negation
(``!``), multiple (whitespace-delimited) patterns per keyword.
- ``HostName``: supplies potential values for ``%h`` :ref:`token expansions
<TOKENS>`.
- ``IdentityFile``: its ability to be specified multiple times and result in a
list of values is preserved in our parser. Values for this keyword will
always be a list of strings, if present.
- ``LocalForward``: like ``IdentityFile``, results in a list of strings.
- ``Port``: supplies potential values for ``%p`` :ref:`token expansions
<TOKENS>`.
- ``ProxyCommand``: see our `.ProxyCommand` class for an easy
way to honor this keyword from a config you've parsed.
- Supports :ref:`expansion tokens <TOKENS>`.
- When a lookup would result in an effective ``ProxyCommand none``,
Paramiko (as of 1.x-2.x) strips it from the resulting dict entirely. A
later major version may retain the ``"none"`` marker for clarity's sake.
- ``RemoteForward``: like ``IdentityFile``, results in a list of strings.
- ``User``: supplies potential values for ``%u`` :ref:`token expansions
<TOKENS>`.
.. _TOKENS:
Expansion tokens
----------------
We support most SSH config expansion tokens where possible, so when they are
present in a config file source, the result of a `.SSHConfig.lookup` will
contain the expansions/substitutions (based on the rest of the config or
properties of the local system).
Specifically, we are known to support the below, where applicable (e.g. as in
OpenSSH, ``%L`` works in ``ControlPath`` but not elsewhere):
- ``%d``
- ``%h``
- ``%l``
- ``%L``
- ``%n``
- ``%p``
- ``%r``
- ``%u``
In addition, we extend OpenSSH's tokens as follows:
- ``~`` is treated like ``%d`` (expands to the local user's home directory
path) when expanding ``ProxyCommand`` values, since ``ProxyCommand`` does not
natively support ``%d`` for some reason.
.. _ssh_config: https://man.openbsd.org/ssh_config
.. _Fabric: http://fabfile.org
``config`` module API documentation
===================================
Mostly of interest to contributors; see previous section for behavioral
details.
.. automodule:: paramiko.config
:member-order: bysource
|
