jeltz/hostap
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Enhance manpage with use of emphasis instead of strong quote

Browse source 
The Debian package checker "lintian" was making noise about
wpa_supplicant.conf(5). It was caused by a line beginning with ', which is
apparently not liked by man(1).

I suggest the use of <emphasis>word</emphasis> where 'word' is used at the
moment.

Signed-off-by: Kel Modderman <kel@otaku42.de>
This commit is contained in:
Kel Modderman 2008-02-27 17:48:23 -08:00 committed by Jouni Malinen
parent 6076f6ce08
commit eff06a7cdb
4 changed files with 25 additions and 24 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
wpa_supplicant/doc/docbook/wpa_cli.sgml
View file

@ -72,17 +72,18 @@
case of OTP request, it includes the challenge from the
authentication server.</para>
<para>The reply to these requests can be given with 'identity',
'password', and 'otp' commands. &lt;id&gt; needs to be copied from the
the matching request. 'password' and 'otp' commands can be used
regardless of whether the request was for PASSWORD or OTP. The
main difference between these two commands is that values given
with 'password' are remembered as long as wpa_supplicant is
running whereas values given with 'otp' are used only once and
then forgotten, i.e., wpa_supplicant will ask frontend for a new
value for every use. This can be used to implement
one-time-password lists and generic token card -based
authentication.</para>
<para>The reply to these requests can be given with
<emphasis>identity</emphasis>, <emphasis>password</emphasis>, and
<emphasis>otp</emphasis> commands. &lt;id&gt; needs to be copied from
the matching request. <emphasis>password</emphasis> and
<emphasis>otp</emphasis> commands can be used regardless of whether
the request was for PASSWORD or OTP. The main difference between these
two commands is that values given with <emphasis>password</emphasis> are
remembered as long as wpa_supplicant is running whereas values given
with <emphasis>otp</emphasis> are used only once and then forgotten,
i.e., wpa_supplicant will ask frontend for a new value for every use.
This can be used to implement one-time-password lists and generic token
card -based authentication.</para>
<para>Example request for password and a matching reply:</para>

8
wpa_supplicant/doc/docbook/wpa_priv.sgml
View file

@ -49,9 +49,9 @@
<title>Example configuration</title>
<para>The following steps are an example of how to configure
<command>wpa_priv</command> to allow users in the 'wpapriv' group
to communicate with <command>wpa_supplicant</command> with privilege
separation:</para>
<command>wpa_priv</command> to allow users in the
<emphasis>wpapriv</emphasis> group to communicate with
<command>wpa_supplicant</command> with privilege separation:</para>
<para>Create user group (e.g., wpapriv) and assign users that
should be able to use wpa_supplicant into that group.</para>
@ -111,7 +111,7 @@ wpa_supplicant -i ath0 -c wpa_supplicant.conf
supported <command>wpa_supplicant</command> driver backends is to be
used. To get a list of supported driver types see wpa_supplicant help
(e.g, wpa_supplicant -h). The driver backend supported by most good
drivers is 'wext'.</para>
drivers is <emphasis>wext</emphasis>.</para>
<para>The &lt;ifname&gt; string specifies which network
interface is to be managed by <command>wpa_supplicant</command>

4
wpa_supplicant/doc/docbook/wpa_supplicant.conf.sgml
View file

@ -26,7 +26,7 @@
<para>Changes to configuration file can be reloaded be sending
SIGHUP signal to <command>wpa_supplicant</command> ('killall -HUP
wpa_supplicant'). Similarly, reloading can be triggered with
the 'wpa_cli reconfigure' command.</para>
the <emphasis>wpa_cli reconfigure</emphasis> command.</para>
<para>Configuration file can include one or more network blocks,
e.g., one for each used SSID. wpa_supplicant will automatically
@ -174,7 +174,7 @@ network={
<listitem>
<para>Authentication for wired Ethernet. This can be used with
'wired' interface (-Dwired on command line).</para>
<emphasis>wired</emphasis> interface (-Dwired on command line).</para>
<blockquote><programlisting>
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel

14
wpa_supplicant/doc/docbook/wpa_supplicant.sgml
View file

@ -530,9 +530,9 @@ wpa_supplicant \
snapshot/v0.2.x)</term>
<listitem>
<para> (http://hostap.epitest.fi/) Driver needs to be set in
Managed mode ('iwconfig wlan0 mode managed'). Please note
that station firmware version needs to be 1.7.0 or newer to
work in WPA mode.</para>
Managed mode (<emphasis>iwconfig wlan0 mode managed</emphasis>).
Please note that station firmware version needs to be 1.7.0 or
newer to work in WPA mode.</para>
</listitem>
</varlistentry>
@ -736,8 +736,8 @@ wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -B
<para>Add MODE="Managed" and WPA="y" to the network scheme in
<filename>/etc/pcmcia/wireless.opts</filename>.</para>
<para>Add the following block to the end of 'start' action handler
in <filename>/etc/pcmcia/wireless</filename>:</para>
<para>Add the following block to the end of <emphasis>start</emphasis>
action handler in <filename>/etc/pcmcia/wireless</filename>:</para>
<blockquote><programlisting>
if [ "$WPA" = "y" -a -x /usr/local/bin/wpa_supplicant ]; then
@ -746,8 +746,8 @@ fi
</programlisting></blockquote>
<para>Add the following block to the end of 'stop' action handler
(may need to be separated from other actions) in
<para>Add the following block to the end of <emphasis>stop</emphasis>
action handler (may need to be separated from other actions) in
<filename>/etc/pcmcia/wireless</filename>:</para>
<blockquote><programlisting>