Re: wpasupplicant udeb
On Monday 26 May 2008 20:46:43 Frans Pop wrote:
> On Sunday 25 May 2008, Kel Modderman wrote:
> > Also, do you think compiling in support for debug messages about
> > association is something that would be useful to have in the
> > debian-installer environment for occasions when manual troubleshooting is
> > required? A fair amount of binary size can be shaved off without it, but
> > unsure if that is wise.
>
> How much difference does it make exactly?
To quote the upstream documentation:
# Remove debugging code that is printing out debug message to stdout.
# This can be used to reduce the size of the wpa_supplicant considerably
# if debugging code is not needed. The size reduction can be around 35%
# (e.g., 90 kB).
#CONFIG_NO_STDOUT_DEBUG=y
> Where do these messages end up? In the syslog or somewhere else?
stdout or to file when the "-f </path/to/file>" command line option is used.
> Can you give an example of these mesages?
There are different message priorities controlled by the -q and -d command line
arguments. Each -d argument given to wpa_supplicant increases verbosity output.
By default the wpa_supplicant daemon prints major events and errors to stdout.
---
Trying to associate with 00:13:10:41:7e:1f (SSID='kelnet' freq=2412 MHz)
Associated with 00:13:10:41:7e:1f
WPA: Key negotiation completed with 00:13:10:41:7e:1f [PTK=TKIP GTK=TKIP]
CTRL-EVENT-CONNECTED - Connection to 00:13:10:41:7e:1f completed (auth) [id=6 id_str=kelnet]
---
Increasing the debug will yield information about wpa_supplicant state machine,
actions and reasons for making actions, and dumps of data being processed.
These can have timestamps too. An example would be too large and uninteresting
to post to this list.
The debugging may not be useful per default, but it could just be worth keeping
so that there is an attack vector for people reporting problems about using a
wpa enabled netcfg, so that they be able to manually invoke wpa_supplicant on
another terminal to capture output for analysis (eg. to find out why
association to desired access point failed). It just depends if this need is
valid and able to offset the desire for very small binary size.
>
>
> Regarding the patch:
> +Depends: ${shlibs:Depends}, dhcp-client-udeb | dhcp3-client-udeb |
> pump-udeb, ethernet-card-detection
>
> Given that wpa-supplicant is only used from within netcfg which already has
> these dependencies, I would say that this can be simplified to:
> +Depends: ${shlibs:Depends}
Thanks, will do that.
>
>
> Other than that the patch looks nice and clean.
> Where is the source repository? I tried to apply the patch to the current
> version in unstable, but that failed miserably...
A recent bug required shuffle around, and provision of arch specific build
configuration handling.
Vcs-Svn: svn://svn.debian.org/pkg-wpa/wpasupplicant/trunk
Vcs-Browser: http://svn.debian.org/wsvn/pkg-wpa/wpasupplicant/trunk/
Thanks, Kel.
Reply to: