| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
The *.ui.h were causing number of warnings and they do not need to be
included in documentation.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Replace " wpa_supplicant" with " %wpa_supplicant" except for
"struct wpa_supplicant". This makes it easier to write Doxygen comments
since there is no need to add the ugly '%' prefix to each instance of
wpa_supplicant text showing up.
|
| |
|
|
|
|
|
| |
No need to use explicit @link command, but must include () after
function name (and in couple of cases, use the current function name).
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The configuration parsing functions seemed to have worked fine before,
but these were real bugs even if they did not show up in practice.
hostapd_ip_diff() was broken for IPv6 addresses (overwrote address and
always returned 1.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This matches the style used in hostapd, i.e., Registrar is initialized
only once and callbacks are now processed in wps_supplicant.c.
|
|
|
|
|
| |
wps_context::registrar can be used as the only location for this
pointer.
|
|
|
|
|
| |
wps_context::ap is available for this purpose and there is no need to
change between AP and not AP between protocol runs.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This updated all doxygen runs to use the same style that was used for
wpa_supplicant full documents. The full vs. fast configurations are now
otherwise identical apart from fast not generating dot files or
latex/pdf version of the documentation.
|
| |
|
| |
|
|
|
|
|
| |
The doxygen run is not exactly warning free yet, but this gets a step
closer to being able to produce something useful again.
|
| |
|
|
|
|
| |
The new WPS code was not setting this in error case.
|
|
|
|
|
| |
Some build configurations failed to compile because this file did not
get included.
|
| |
|
|
|
|
|
|
| |
Generate a SHA1 hash -based UUID from the local MAC address if the UUID
was not configured. This makes it easier to prepare for WPS since there
is no need to generate an UUID.
|
|
|
|
|
| |
No need to configure these separately for each Enrollee in wps_config
since wps_context is now used both for Registrar and Enrollee.
|
|
|
|
|
| |
This can be used to get rid of the extra cpp define since we have our
local copy of wireless.h and nl80211.h.
|
| |
|
| |
|
|
|
|
|
|
| |
When using ap_scan=1, we know before the association request that MFP
will be supported, so we can as well require it. This helps mac80211 in
configuring whether to enable MFP.
|
|
|
|
|
|
|
| |
IEEE 802.11w/D7.0 incorrectly changed the Action Category from 8 to 7
when renaming Ping to SA Query. Category 7 is reserved for HT (IEEE
802.11n) and IEEE 802.11w will need to continue to use the category 8
that was allocated for it.
|
|
|
|
| |
Do not send extra 24 octets of random data in the end.
|
| |
|
|
|
|
|
|
| |
mac80211 can now figure out which key to use for injected frames (in
most cases), so we can remove the workaround for configuring IGTK on the
monitor interface that is used for injecting frames.
|
|
|
|
|
| |
This can be useful for testing IEEE 802.11w functionality, so provide
means for manual request to send a SA Query request.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previous version assumed that the Flags field is always present and
ended up reading one octet past the end of the buffer should the Flags
field be missing. The message length would also be set incorrectly
(size_t)-1 or (size_t)-5, but it looks like reassembly code ended up
failing in malloc before actually using this huge length to read data.
RFC 2716 uses a somewhat unclear description on what exactly is included
in the TLS Ack message ("no data" can refer to either Data field in 4.1
or TLS Data field in 4.2), so in theory, it would be possible for some
implementations to not include Flags field. However,
EAP-{PEAP,TTLS,FAST} need the Flags field in Ack messages, too, for
indicating the used version.
The EAP peer code will now accept the no-Flags case as an Ack message if
EAP workarounds are enabled (which is the default behavior). If
workarounds are disabled, the message without Flags field will be
rejected.
[Bug 292]
|
|
|
|
|
|
|
|
|
|
| |
There is not really much else the Authenticator can do if it does not
receive valid EAP response from the Supplicant/EAP peer. EAP-Failure
would need to be sent before trying to start again with
EAP-Request/Identity, but that is not allowed before the EAP peer
actually replies. Anyway, forcing a new association is likely to clean
up peer state, too, so it can help fixing some issues that could have
caused the peer not to be able to reply in the first place.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It looks like this never survived the move from IEEE 802.1X-2001 to
IEEE 802.1X-2004 and EAP state machine (RFC 4137). The retransmission
scheduling and control is now in EAP authenticator and the
calculateTimeout() producedure is used to determine timeout for
retransmission (either dynamic backoff or value from EAP method hint).
The recommended calculations based on SRTT and RTTVAR (RFC 2988) are not
yet implemented since there is no round-trip time measurement available
yet.
This should make EAP authentication much more robust in environments
where initial packets are lost for any reason. If the EAP method does
not provide a hint on timeout, default schedule of 3, 6, 12, 20, 20, 20,
... seconds will be used.
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, only the delivery option 1 from RFC 4284
(EAP-Request/Identity from the AP) was supported. Now option 3
(subsequent EAP-Request/Identity from RADIUS server) can also be used
when hostapd is used as a RADIUS server. The eap_user file will need to
have a Phase 1 user entry pointing to Identity method in order for this
to happen (e.g., "* Identity" in the end of the file). The identity hint
is configured in the same was as for AP/Authenticator case (eap_message
in hostapd.conf).
|
|
|
|
|
| |
It looks like we need base64 routines when compiling WPS in hostapd
(used in src/wps/wps_registrar.c:910).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The previous max_attempts * timeout is now replaced with two timeouts
(one for each retry, the other one for maximum wait).
|