67
64
><replaceable>PORT</replaceable></option></arg>
71
68
<arg choice="plain"><option>--interface
72
<replaceable>NAME</replaceable><arg rep='repeat'
73
>,<replaceable>NAME</replaceable></arg></option></arg>
74
<arg choice="plain"><option>-i <replaceable>NAME</replaceable
75
><arg rep='repeat'>,<replaceable>NAME</replaceable></arg
69
<replaceable>NAME</replaceable></option></arg>
70
<arg choice="plain"><option>-i
71
<replaceable>NAME</replaceable></option></arg>
142
137
communicates with <citerefentry><refentrytitle
143
138
>mandos</refentrytitle><manvolnum>8</manvolnum></citerefentry>
144
139
to get a password. In slightly more detail, this client program
145
brings up network interfaces, uses the interfaces’ IPv6
146
link-local addresses to get network connectivity, uses Zeroconf
147
to find servers on the local network, and communicates with
148
servers using TLS with an OpenPGP key to ensure authenticity and
140
brings up a network interface, uses the interface’s IPv6
141
link-local address to get network connectivity, uses Zeroconf to
142
find servers on the local network, and communicates with servers
143
using TLS with an OpenPGP key to ensure authenticity and
149
144
confidentiality. This client program keeps running, trying all
150
145
servers on the network, until it receives a satisfactory reply
151
146
or a TERM signal. After all servers have been tried, all
153
148
will wait indefinitely for new servers to appear.
156
The network interfaces are selected like this: If any interfaces
157
are specified using the <option>--interface</option> option,
158
those interface are used. Otherwise,
159
<command>&COMMANDNAME;</command> will use all interfaces that
160
are not loopback interfaces, are not point-to-point interfaces,
161
are capable of broadcasting and do not have the NOARP flag (see
151
The network interface is selected like this: If an interface is
152
specified using the <option>--interface</option> option, that
153
interface is used. Otherwise, <command>&COMMANDNAME;</command>
154
will choose any interface that is up and running and is not a
155
loopback interface, is not a point-to-point interface, is
156
capable of broadcasting and does not have the NOARP flag (see
162
157
<citerefentry><refentrytitle>netdevice</refentrytitle>
163
158
<manvolnum>7</manvolnum></citerefentry>). (If the
164
159
<option>--connect</option> option is used, point-to-point
165
interfaces and non-broadcast interfaces are accepted.) If any
166
used interfaces are not up and running, they are first taken up
167
(and later taken down again on program exit).
160
interfaces and non-broadcast interfaces are accepted.) If no
161
acceptable interfaces are found, re-run the check but without
162
the <quote>up and running</quote> requirement, and manually take
163
the selected interface up (and later take it down on program
170
Before network interfaces are selected, all <quote>network
167
Before a network interface is selected, all <quote>network
171
168
hooks</quote> are run; see <xref linkend="network-hooks"/>.
221
218
assumed to separate the address from the port number.
224
Normally, Zeroconf would be used to locate Mandos servers,
225
in which case this option would only be used when testing
221
This option is normally only useful for testing and
232
228
<term><option>--interface=<replaceable
233
>NAME</replaceable><arg rep='repeat'>,<replaceable
234
>NAME</replaceable></arg></option></term>
229
>NAME</replaceable></option></term>
236
<replaceable>NAME</replaceable><arg rep='repeat'>,<replaceable
237
>NAME</replaceable></arg></option></term>
231
<replaceable>NAME</replaceable></option></term>
240
Comma separated list of network interfaces that will be
241
brought up and scanned for Mandos servers to connect to.
242
The default is the empty string, which will automatically
243
use all appropriate interfaces.
234
Network interface that will be brought up and scanned for
235
Mandos servers to connect to. The default is the empty
236
string, which will automatically choose an appropriate
246
If the <option>--connect</option> option is used, and
247
exactly one interface name is specified (except
248
<quote><literal>none</literal></quote>), this specifies
249
the interface to use to connect to the address given.
240
If the <option>--connect</option> option is used, this
241
specifies the interface to use to connect to the address
252
245
Note that since this program will normally run in the
253
246
initial RAM disk environment, the interface must be an
254
247
interface which exists at that stage. Thus, the interface
255
can normally not be a pseudo-interface such as
256
<quote>br0</quote> or <quote>tun0</quote>; such interfaces
257
will not exist until much later in the boot process, and
258
can not be used by this program, unless created by a
259
<quote>network hook</quote> — see <xref
260
linkend="network-hooks"/>.
248
can not be a pseudo-interface such as <quote>br0</quote>
249
or <quote>tun0</quote>; such interfaces will not exist
250
until much later in the boot process, and can not be used
251
by this program, unless created by a <quote>network
252
hook</quote> — see <xref linkend="network-hooks"/>.
263
255
<replaceable>NAME</replaceable> can be the string
264
<quote><literal>none</literal></quote>; this will make
265
<command>&COMMANDNAME;</command> only bring up interfaces
266
specified <emphasis>before</emphasis> this string. This
267
is not recommended, and only meant for advanced users.
256
<quote><literal>none</literal></quote>; this will not use
257
any specific interface, and will not bring up an interface
258
on startup. This is not recommended, and only meant for
446
438
<refsect1 id="environment">
447
439
<title>ENVIRONMENT</title>
450
<term><envar>MANDOSPLUGINHELPERDIR</envar></term>
453
This environment variable will be assumed to contain the
454
directory containing any helper executables. The use and
455
nature of these helper executables, if any, is
456
purposefully not documented.
462
This program does not use any other environment variables, not
463
even the ones provided by <citerefentry><refentrytitle
441
This program does not use any environment variables, not even
442
the ones provided by <citerefentry><refentrytitle
464
443
>cryptsetup</refentrytitle><manvolnum>8</manvolnum>
568
547
<term><envar>DEVICE</envar></term>
571
The network interfaces, as specified to
550
The network interface, as specified to
572
551
<command>&COMMANDNAME;</command> by the
573
<option>--interface</option> option, combined to one
574
string and separated by commas. If this is set, and
575
does not contain the interface a hook will bring up,
576
there is no reason for a hook to continue.
552
<option>--interface</option> option. If this is not the
553
interface a hook will bring up, there is no reason for a
763
741
It will also help if the checker program on the server is
764
742
configured to request something from the client which can not be
765
spoofed by someone else on the network, like SSH server key
766
fingerprints, and unlike unencrypted <acronym>ICMP</acronym>
767
echo (<quote>ping</quote>) replies.
743
spoofed by someone else on the network, unlike unencrypted
744
<acronym>ICMP</acronym> echo (<quote>ping</quote>) replies.
770
747
<emphasis>Note</emphasis>: This makes it completely insecure to
added
removed
plugins.d/mandos-client.xml
