1<!doctype refentry PUBLIC "-//OASIS//DTD DocBook V4.1//EN">
2
3<refentry>
4  <refentryinfo>
5    <date>07 August 2019</date>
6  </refentryinfo>
7
8  <refmeta>
9    <refentrytitle>wpa_supplicant</refentrytitle>
10    <manvolnum>8</manvolnum>
11  </refmeta>
12  <refnamediv>
13    <refname>wpa_supplicant</refname>
14    <refpurpose>Wi-Fi Protected Access client and IEEE 802.1X supplicant</refpurpose>
15  </refnamediv>
16  <refsynopsisdiv>
17    <cmdsynopsis>
18      <command>wpa_supplicant</command>
19      <arg>-BddfhKLqqsTtuvW</arg>
20      <arg>-i<replaceable>ifname</replaceable></arg>
21      <arg>-c<replaceable>config file</replaceable></arg>
22      <arg>-D<replaceable>driver</replaceable></arg>
23      <arg>-P<replaceable>PID_file</replaceable></arg>
24      <arg>-f<replaceable>output file</replaceable></arg>
25    </cmdsynopsis>
26  </refsynopsisdiv>
27  <refsect1>
28    <title>Overview</title>
29
30    <para>
31    Wireless networks do not require physical access to the network equipment
32    in the same way as wired networks. This makes it easier for unauthorized
33    users to passively monitor a network and capture all transmitted frames.
34    In addition, unauthorized use of the network is much easier. In many cases,
35    this can happen even without user's explicit knowledge since the wireless
36    LAN adapter may have been configured to automatically join any available
37    network.
38    </para>
39
40    <para>
41    Link-layer encryption can be used to provide a layer of security for
42    wireless networks. The original wireless LAN standard, IEEE 802.11,
43    included a simple encryption mechanism, WEP. However, that proved to
44    be flawed in many areas and network protected with WEP cannot be consider
45    secure. IEEE 802.1X authentication and frequently changed dynamic WEP keys
46    can be used to improve the network security, but even that has inherited
47    security issues due to the use of WEP for encryption. Wi-Fi Protected
48    Access and IEEE 802.11i amendment to the wireless LAN standard introduce
49    a much improved mechanism for securing wireless networks. IEEE 802.11i
50    enabled networks that are using CCMP (encryption mechanism based on strong
51    cryptographic algorithm AES) can finally be called secure used for
52    applications which require efficient protection against unauthorized
53    access.
54    </para>
55
56    <para><command>wpa_supplicant</command> is an implementation of
57    the WPA Supplicant component, i.e., the part that runs in the
58    client stations. It implements WPA key negotiation with a WPA
59    Authenticator and EAP authentication with Authentication
60    Server. In addition, it controls the roaming and IEEE 802.11
61    authentication/association of the wireless LAN driver.</para>
62
63    <para><command>wpa_supplicant</command> is designed to be a
64    "daemon" program that runs in the background and acts as the
65    backend component controlling the wireless
66    connection. <command>wpa_supplicant</command> supports separate
67    frontend programs and an example text-based frontend,
68    <command>wpa_cli</command>, is included with
69    wpa_supplicant.</para>
70
71    <para>Before wpa_supplicant can do its work, the network interface
72    must be available.  That means that the physical device must be
73    present and enabled, and the driver for the device must be
74    loaded. The daemon will exit immediately if the device is not already
75    available.</para>
76
77    <para>After <command>wpa_supplicant</command> has configured the
78    network device, higher level configuration such as DHCP may
79    proceed.  There are a variety of ways to integrate wpa_supplicant
80    into a machine's networking scripts, a few of which are described
81    in sections below.</para>
82
83    <para>The following steps are used when associating with an AP
84    using WPA:</para>
85
86    <itemizedlist>
87      <listitem>
88	<para><command>wpa_supplicant</command> requests the kernel
89	driver to scan neighboring BSSes</para>
90      </listitem>
91
92      <listitem>
93	<para><command>wpa_supplicant</command> selects a BSS based on
94	its configuration</para>
95      </listitem>
96
97      <listitem>
98	<para><command>wpa_supplicant</command> requests the kernel
99        driver to associate with the chosen BSS</para>
100      </listitem>
101
102      <listitem>
103	<para>If WPA-EAP: integrated IEEE 802.1X Supplicant
104        completes EAP authentication with the
105        authentication server (proxied by the Authenticator in the
106        AP)</para>
107      </listitem>
108
109      <listitem>
110	<para>If WPA-EAP: master key is received from the IEEE 802.1X
111	Supplicant</para>
112      </listitem>
113
114      <listitem>
115	<para>If WPA-PSK: <command>wpa_supplicant</command> uses PSK
116	as the master session key</para>
117      </listitem>
118
119      <listitem>
120	<para><command>wpa_supplicant</command> completes WPA 4-Way
121        Handshake and Group Key Handshake with the Authenticator
122        (AP)</para>
123      </listitem>
124
125      <listitem>
126	<para><command>wpa_supplicant</command> configures encryption
127	keys for unicast and broadcast</para>
128      </listitem>
129
130      <listitem>
131	<para>normal data packets can be transmitted and received</para>
132      </listitem>
133    </itemizedlist>
134  </refsect1>
135
136  <refsect1>
137    <title>Supported Features</title>
138    <para>Supported WPA/IEEE 802.11i features:</para>
139    <itemizedlist>
140      <listitem>
141	<para>WPA-PSK ("WPA-Personal")</para>
142      </listitem>
143
144      <listitem>
145	<para>WPA with EAP (e.g., with RADIUS authentication server)
146       ("WPA-Enterprise") Following authentication methods are
147       supported with an integrate IEEE 802.1X Supplicant:</para>
148
149	<itemizedlist>
150	  <listitem>
151	    <para>EAP-TLS</para>
152	  </listitem>
153	</itemizedlist>
154
155	<itemizedlist>
156	  <listitem>
157	    <para>EAP-PEAP/MSCHAPv2 (both PEAPv0 and PEAPv1)</para>
158	  </listitem>
159
160
161	  <listitem>
162	    <para>EAP-PEAP/TLS (both PEAPv0 and PEAPv1)</para>
163	  </listitem>
164
165	  <listitem>
166	    <para>EAP-PEAP/GTC (both PEAPv0 and PEAPv1)</para>
167	  </listitem>
168
169	  <listitem>
170	    <para>EAP-PEAP/OTP (both PEAPv0 and PEAPv1)</para>
171	  </listitem>
172
173	  <listitem>
174	    <para>EAP-PEAP/MD5-Challenge (both PEAPv0 and PEAPv1)</para>
175	  </listitem>
176
177	  <listitem>
178	    <para>EAP-TTLS/EAP-MD5-Challenge</para>
179	  </listitem>
180
181	  <listitem>
182	    <para>EAP-TTLS/EAP-GTC</para>
183	  </listitem>
184
185          <listitem><para>EAP-TTLS/EAP-OTP</para></listitem>
186
187          <listitem><para>EAP-TTLS/EAP-MSCHAPv2</para></listitem>
188
189          <listitem><para>EAP-TTLS/EAP-TLS</para></listitem>
190
191          <listitem><para>EAP-TTLS/MSCHAPv2</para></listitem>
192
193          <listitem><para>EAP-TTLS/MSCHAP</para></listitem>
194
195          <listitem><para>EAP-TTLS/PAP</para></listitem>
196
197          <listitem><para>EAP-TTLS/CHAP</para></listitem>
198
199          <listitem><para>EAP-SIM</para></listitem>
200
201          <listitem><para>EAP-AKA</para></listitem>
202
203          <listitem><para>EAP-PSK</para></listitem>
204
205          <listitem><para>EAP-PAX</para></listitem>
206
207          <listitem><para>LEAP (note: requires special support from
208          the driver for IEEE 802.11 authentication)</para></listitem>
209
210          <listitem><para>(following methods are supported, but since
211          they do not generate keying material, they cannot be used
212          with WPA or IEEE 802.1X WEP keying)</para></listitem>
213
214          <listitem><para>EAP-MD5-Challenge </para></listitem>
215
216          <listitem><para>EAP-MSCHAPv2</para></listitem>
217
218          <listitem><para>EAP-GTC</para></listitem>
219
220          <listitem><para>EAP-OTP</para></listitem>
221	</itemizedlist>
222      </listitem>
223
224      <listitem>
225	<para>key management for CCMP, TKIP, WEP104, WEP40</para>
226      </listitem>
227
228      <listitem>
229	<para>RSN/WPA2 (IEEE 802.11i)</para>
230	<itemizedlist>
231	  <listitem>
232	    <para>pre-authentication</para>
233	  </listitem>
234
235	  <listitem>
236	    <para>PMKSA caching</para>
237	  </listitem>
238	</itemizedlist>
239      </listitem>
240    </itemizedlist>
241  </refsect1>
242
243  <refsect1>
244    <title>Available Drivers</title>
245    <para>A summary of available driver backends is below. Support for each
246    of the driver backends is chosen at wpa_supplicant compile time. For a
247    list of supported driver backends that may be used with the -D option on
248    your system, refer to the help output of wpa_supplicant
249    (<emphasis>wpa_supplicant -h</emphasis>).</para>
250
251    <variablelist>
252      <varlistentry>
253	<term>nl80211</term>
254	<listitem>
255	  <para>Uses the modern Linux nl80211/cfg80211 netlink-based
256	  interface (most new drivers).</para>
257	</listitem>
258      </varlistentry>
259
260      <varlistentry>
261	<term>wext</term>
262	<listitem>
263	  <para>Uses the legacy Linux wireless extensions ioctl-based
264	  interface (older hardware/drivers).</para>
265	</listitem>
266      </varlistentry>
267
268      <varlistentry>
269	<term>wired</term>
270	<listitem>
271	  <para>wpa_supplicant wired Ethernet driver</para>
272	</listitem>
273      </varlistentry>
274
275      <varlistentry>
276	<term>roboswitch</term>
277	<listitem>
278	  <para>wpa_supplicant Broadcom switch driver</para>
279	</listitem>
280      </varlistentry>
281
282      <varlistentry>
283	<term>bsd</term>
284	<listitem>
285	  <para>BSD 802.11 support (Atheros, etc.).</para>
286	</listitem>
287      </varlistentry>
288
289      <varlistentry>
290	<term>ndis</term>
291	<listitem>
292	  <para>Windows NDIS driver.</para>
293	</listitem>
294      </varlistentry>
295    </variablelist>
296  </refsect1>
297
298  <refsect1>
299    <title>Command Line Options</title>
300    <para>Most command line options have global scope. Some are given per
301    interface, and are only valid if at least one <option>-i</option> option
302    is specified, otherwise they're ignored. Option groups for different
303    interfaces must be separated by <option>-N</option> option.</para>
304    <variablelist>
305      <varlistentry>
306	<term>-b br_ifname</term>
307	<listitem>
308	  <para>Optional bridge interface name. (Per interface)</para>
309	</listitem>
310      </varlistentry>
311
312      <varlistentry>
313	<term>-B</term>
314	<listitem>
315	  <para>Run daemon in the background.</para>
316	</listitem>
317      </varlistentry>
318
319      <varlistentry>
320	<term>-c filename</term>
321	<listitem>
322	  <para>Path to configuration file. (Per interface)</para>
323	</listitem>
324      </varlistentry>
325
326      <varlistentry>
327	<term>-C ctrl_interface</term>
328	<listitem>
329	  <para>Path to ctrl_interface socket (Per interface. Only used if
330		  <option>-c</option> is not).</para>
331	</listitem>
332      </varlistentry>
333
334      <varlistentry>
335	<term>-i ifname</term>
336	<listitem>
337	  <para>Interface to listen on. Multiple instances of this option can
338	  be present, one per interface, separated by <option>-N</option>
339	  option (see below).</para>
340	</listitem>
341      </varlistentry>
342
343      <varlistentry>
344	<term>-d</term>
345	<listitem>
346	  <para>Increase debugging verbosity (<option>-dd</option> even
347		  more).</para>
348	</listitem>
349      </varlistentry>
350
351      <varlistentry>
352	<term>-D driver</term>
353	<listitem>
354	  <para>Driver to use (can be multiple drivers: nl80211,wext).
355		  (Per interface, see the available options below.)</para>
356	</listitem>
357      </varlistentry>
358
359      <varlistentry>
360	<term>-e entropy file</term>
361	<listitem>
362	  <para>File for <command>wpa_supplicant</command> to use to
363	  maintain its internal entropy store in over restarts.</para>
364	</listitem>
365      </varlistentry>
366
367      <varlistentry>
368	<term>-f output file</term>
369	<listitem>
370	  <para>Log output to specified file instead of stdout. (This
371	  is only available if <command>wpa_supplicant</command> was
372	  built with the <literal>CONFIG_DEBUG_FILE</literal>
373	  option.)</para>
374	</listitem>
375      </varlistentry>
376
377      <varlistentry>
378	<term>-g global ctrl_interface</term>
379	<listitem>
380	  <para>Path to global ctrl_interface socket. If specified, interface
381	  definitions may be omitted.</para>
382	</listitem>
383      </varlistentry>
384
385      <varlistentry>
386	<term>-K</term>
387	<listitem>
388	  <para>Include keys (passwords, etc.) in debug output.</para>
389	</listitem>
390      </varlistentry>
391
392      <varlistentry>
393	<term>-h</term>
394	<listitem>
395	  <para>Help.  Show a usage message.</para>
396	</listitem>
397      </varlistentry>
398
399      <varlistentry>
400	<term>-L</term>
401	<listitem>
402	  <para>Show license (BSD).</para>
403	</listitem>
404      </varlistentry>
405
406      <varlistentry>
407	<term>-o override driver</term>
408	<listitem>
409	  <para>Override the driver parameter for new
410	  interfaces.</para>
411	</listitem>
412      </varlistentry>
413
414      <varlistentry>
415	<term>-O override ctrl_interface</term>
416	<listitem>
417	  <para>Override the ctrl_interface parameter for new
418	  interfaces.</para>
419	</listitem>
420      </varlistentry>
421
422      <varlistentry>
423	<term>-p</term>
424	<listitem>
425	  <para>Driver parameters. (Per interface)</para>
426	</listitem>
427      </varlistentry>
428
429      <varlistentry>
430	<term>-P PID_file</term>
431	<listitem>
432	  <para>Path to PID file.</para>
433	</listitem>
434      </varlistentry>
435
436      <varlistentry>
437	<term>-q</term>
438	<listitem>
439	  <para>Decrease debugging verbosity (<option>-qq</option> even
440		  less).</para>
441	</listitem>
442      </varlistentry>
443
444      <varlistentry>
445	<term>-s</term>
446	<listitem>
447	  <para>Log output to syslog instead of stdout. (This is only
448	  available if <command>wpa_supplicant</command> was built
449	  with the <literal>CONFIG_DEBUG_SYSLOG</literal>
450	  option.)</para>
451	</listitem>
452      </varlistentry>
453
454      <varlistentry>
455	<term>-T</term>
456	<listitem>
457	  <para>Log output to Linux tracing in addition to any other
458	  destinations. (This is only available
459	  if <command>wpa_supplicant</command> was built with
460	  the <literal>CONFIG_DEBUG_LINUX_TRACING</literal>
461	  option.)</para>
462	</listitem>
463      </varlistentry>
464
465      <varlistentry>
466	<term>-t</term>
467	<listitem>
468	  <para>Include timestamp in debug messages.</para>
469	</listitem>
470      </varlistentry>
471
472      <varlistentry>
473	<term>-u</term>
474	<listitem>
475	  <para>Enable DBus control interface. If enabled, interface
476	  definitions may be omitted. (This is only available
477	  if <command>wpa_supplicant</command> was built with
478	  the <literal>CONFIG_CTRL_IFACE_DBUS_NEW</literal> option.)</para>
479	</listitem>
480      </varlistentry>
481
482      <varlistentry>
483	<term>-v</term>
484	<listitem>
485	  <para>Show version.</para>
486	</listitem>
487      </varlistentry>
488
489      <varlistentry>
490	<term>-W</term>
491	<listitem>
492	  <para>Wait for a control interface monitor before starting.</para>
493	</listitem>
494      </varlistentry>
495
496      <varlistentry>
497	<term>-N</term>
498	<listitem>
499	  <para>Start describing new interface.</para>
500	</listitem>
501      </varlistentry>
502    </variablelist>
503  </refsect1>
504
505  <refsect1>
506    <title>Examples</title>
507
508    <para>In most common cases, <command>wpa_supplicant</command> is
509    started with:</para>
510
511<blockquote><programlisting>
512wpa_supplicant -B -c/etc/wpa_supplicant.conf -iwlan0
513</programlisting></blockquote>
514
515    <para>This makes the process fork into background.</para>
516
517    <para>The easiest way to debug problems, and to get debug log for
518    bug reports, is to start <command>wpa_supplicant</command> on
519    foreground with debugging enabled:</para>
520
521<blockquote><programlisting>
522wpa_supplicant -c/etc/wpa_supplicant.conf -iwlan0 -d
523</programlisting></blockquote>
524
525    <para>If the specific driver wrapper is not known beforehand, it is
526    possible to specify multiple comma separated driver wrappers on the command
527    line. <command>wpa_supplicant</command> will use the first driver
528    wrapper that is able to initialize the interface.</para>
529
530<blockquote><programlisting>
531wpa_supplicant -Dnl80211,wext -c/etc/wpa_supplicant.conf -iwlan0
532</programlisting></blockquote>
533
534    <para><command>wpa_supplicant</command> can control multiple
535    interfaces (radios) either by running one process for each
536    interface separately or by running just one process and list of
537    options at command line. Each interface is separated with -N
538    argument. As an example, following command would start
539    wpa_supplicant for two interfaces:</para>
540
541<blockquote><programlisting>
542wpa_supplicant \
543	-c wpa1.conf -i wlan0 -D nl80211 -N \
544	-c wpa2.conf -i ath0 -D wext
545</programlisting></blockquote>
546  </refsect1>
547
548  <refsect1>
549    <title>OS Requirements</title>
550    <para>Current hardware/software requirements:</para>
551
552    <itemizedlist>
553      <listitem>
554	<para>Linux kernel 2.6.30 or higher with
555	nl80211/cfg80211 support</para>
556      </listitem>
557
558      <listitem>
559	<para>Linux kernel 2.4.x or higher with Linux Wireless
560	Extensions v15 or newer</para>
561      </listitem>
562
563      <listitem>
564	<para>FreeBSD 6-CURRENT</para>
565      </listitem>
566
567      <listitem>
568	<para>Microsoft Windows with WinPcap (at least WinXP, may work
569	with other versions)</para>
570      </listitem>
571    </itemizedlist>
572  </refsect1>
573
574  <refsect1>
575    <title>Supported Drivers</title>
576    <variablelist>
577      <varlistentry>
578	<term>Linux nl80211/cfg80211</term>
579	<listitem>
580	  <para>This is the preferred driver for Linux.</para>
581	</listitem>
582      </varlistentry>
583
584      <varlistentry>
585	<term>Linux wireless extensions</term>
586	<listitem>
587	  <para>In theory, any driver that supports Linux wireless
588	extensions can be used with IEEE 802.1X (i.e., not WPA) when
589	using ap_scan=0 option in configuration file.</para>
590	</listitem>
591      </varlistentry>
592
593      <varlistentry>
594	<term>Wired Ethernet drivers</term>
595	<listitem>
596	  <para>Use ap_scan=0.</para>
597	</listitem>
598      </varlistentry>
599
600      <varlistentry>
601	<term>BSD net80211 layer (e.g., Atheros driver)</term>
602	<listitem>
603	  <para>At the moment, this is for FreeBSD 6-CURRENT branch.</para>
604	</listitem>
605      </varlistentry>
606
607      <varlistentry>
608	<term>Windows NDIS</term>
609	<listitem>
610	  <para>The current Windows port requires WinPcap
611	(http://winpcap.polito.it/).  See README-Windows.txt for more
612	information.</para>
613	</listitem>
614      </varlistentry>
615    </variablelist>
616
617
618    <para>wpa_supplicant was designed to be portable for different
619    drivers and operating systems. Hopefully, support for more wlan
620    cards and OSes will be added in the future. See developer.txt for
621    more information about the design of wpa_supplicant and porting to
622    other drivers. One main goal is to add full WPA/WPA2 support to
623    Linux wireless extensions to allow new drivers to be supported
624    without having to implement new driver-specific interface code in
625    wpa_supplicant.</para>
626  </refsect1>
627
628  <refsect1>
629    <title>Architecture</title> <para>The
630    <command>wpa_supplicant</command> system consists of the following
631    components:</para>
632
633    <variablelist>
634      <varlistentry>
635	<term><filename>wpa_supplicant.conf</filename> </term>
636	<listitem>
637        <para>the configuration file describing all networks that the
638        user wants the computer to connect to.  </para>
639	</listitem>
640      </varlistentry>
641      <varlistentry>
642	<term><command>wpa_supplicant</command></term>
643        <listitem><para>the program that directly interacts with the
644        network interface.  </para></listitem>
645      </varlistentry>
646      <varlistentry>
647	<term><command>wpa_cli</command></term> <listitem><para> the
648	client program that provides a high-level interface to the
649	functionality of the daemon.  </para></listitem>
650      </varlistentry>
651      <varlistentry>
652	<term><command>wpa_passphrase</command></term>
653        <listitem><para>a utility needed to construct
654        <filename>wpa_supplicant.conf</filename> files that include
655        encrypted passwords.</para></listitem>
656      </varlistentry>
657    </variablelist>
658  </refsect1>
659
660  <refsect1>
661    <title>Quick Start</title>
662
663    <para>First, make a configuration file, e.g.
664    <filename>/etc/wpa_supplicant.conf</filename>, that describes the networks
665    you are interested in.  See <citerefentry>
666	<refentrytitle>wpa_supplicant.conf</refentrytitle>
667	<manvolnum>5</manvolnum>
668      </citerefentry>
669    for details.</para>
670
671    <para>Once the configuration is ready, you can test whether the
672    configuration works by running <command>wpa_supplicant</command>
673    with following command to start it on foreground with debugging
674    enabled:</para>
675
676    <blockquote><programlisting>
677wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -d
678    </programlisting></blockquote>
679
680    <para>Assuming everything goes fine, you can start using following
681    command to start <command>wpa_supplicant</command> on background
682    without debugging:</para>
683
684    <blockquote><programlisting>
685wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -B
686    </programlisting></blockquote>
687
688    <para>Please note that if you included more than one driver
689    interface in the build time configuration (.config), you may need
690    to specify which interface to use by including -D&lt;driver
691    name&gt; option on the command line.</para>
692
693    <!-- XXX at this point, the page could include a little script
694         based on wpa_cli to wait for a connection and then run
695         dhclient -->
696
697  </refsect1>
698
699  <refsect1>
700    <title>Interface to pcmcia-cs/cardmrg</title>
701
702    <para>For example, following small changes to pcmcia-cs scripts
703    can be used to enable WPA support:</para>
704
705    <para>Add MODE="Managed" and WPA="y" to the network scheme in
706    <filename>/etc/pcmcia/wireless.opts</filename>.</para>
707
708    <para>Add the following block to the end of <emphasis>start</emphasis>
709    action handler in <filename>/etc/pcmcia/wireless</filename>:</para>
710
711    <blockquote><programlisting>
712if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
713    /usr/local/bin/wpa_supplicant -B -c/etc/wpa_supplicant.conf -i$DEVICE
714fi
715    </programlisting></blockquote>
716
717
718    <para>Add the following block to the end of <emphasis>stop</emphasis>
719    action handler (may need to be separated from other actions) in
720    <filename>/etc/pcmcia/wireless</filename>:</para>
721
722    <blockquote><programlisting>
723if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
724    killall wpa_supplicant
725fi
726    </programlisting></blockquote>
727
728    <para>This will make <command>cardmgr</command> start
729    <command>wpa_supplicant</command> when the card is plugged
730    in.</para>
731  </refsect1>
732
733  <refsect1>
734    <title>See Also</title>
735    <para>
736      <citerefentry>
737	<refentrytitle>wpa_background</refentrytitle>
738	<manvolnum>8</manvolnum>
739      </citerefentry>
740      <citerefentry>
741	<refentrytitle>wpa_supplicant.conf</refentrytitle>
742	<manvolnum>5</manvolnum>
743      </citerefentry>
744      <citerefentry>
745	<refentrytitle>wpa_cli</refentrytitle>
746	<manvolnum>8</manvolnum>
747      </citerefentry>
748      <citerefentry>
749	<refentrytitle>wpa_passphrase</refentrytitle>
750	<manvolnum>8</manvolnum>
751      </citerefentry>
752    </para>
753  </refsect1>
754  <refsect1>
755    <title>Legal</title>
756    <para>wpa_supplicant is copyright (c) 2003-2019,
757    Jouni Malinen <email>j@w1.fi</email> and
758    contributors.
759    All Rights Reserved.</para>
760
761    <para>This program is licensed under the BSD license (the one with
762    advertisement clause removed).</para>
763  </refsect1>
764</refentry>
765