| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
This patch adds support for wired IEEE 802.1X client on the Solaris.
I have tested with these:
OS : OpenSolaris 2009.06
EAP : EAP-MD5
Switch : Cisco Catalyst 2950
|
|
|
|
|
|
| |
The arithmetic on void pointer exists in trace routine. On GNU C, it
works because void pointer size is 1, but not all compilers behave like
this. So this patch specifies the size of the pointer.
|
|
|
|
|
|
|
| |
Some frequent debug prints are of limited use and make debug output
difficult to read. Make them use a new debug level so that -dd
provides more readable output (-ddd can now be used to enable
the excessive debug prints).
|
|
|
|
|
| |
It is possible that the timeout pointer becomes invalid in one of the
signal handlers, so we need to reload the pointer after those.
|
|
|
|
|
|
| |
There are no subdirectories in any of these directories or plans
for adding ones. As such, there is no point in running the loop
that does not do anything and can cause problems with some shells.
|
|
|
|
|
|
|
| |
This version of the MAC address parser allows number of different
string formats for the address (e.g., 00:11:22:33:44:55, 0011.2233.4455,
001122334455, 00-11-22-33-44-55). It returns the number of characters
used from the input string in case of success.
|
| |
|
|
|
|
|
|
|
|
| |
This patch allows wpa_supplicant to compile on Debian's kfreebsd
architectures.
Patch by Stefan Lippers-Hollmann based on work done by Petr Salinger
and Emmanuel Bouthenot for 0.6.X (http://bugs.debian.org/480572).
|
|
|
|
|
|
|
| |
Better make sure the eloop_timeout data gets fully initialized. The
current code is filling in all the fields, but it is clearer to just
zero the buffer to make sure any new field added to the structure gets
initialized.
|
|
|
|
| |
On FreeBSD 8.0, WPA_TRACE and WPA_TRACE_BFD functionality build fails.
|
| |
|
| |
|
|
|
|
|
| |
We need to copy not only the context pointers, but also the function
pointer before the timeout gets freed.
|
|
|
|
|
| |
This avoids bogus error reports for cases where the timeout handler
frees the memory that was pointed to by the eloop timeout context.
|
| |
|
|
|
|
|
|
| |
This structure is embedded in some other structures and as such, it
would be nicer if this would not change its length based on build
options.
|
| |
|
|
|
|
|
|
| |
This filters out the functions inside trace.c and functions before
main() since those are not relevant to the actual issue that is being
reported.
|
|
|
|
|
|
|
|
| |
This WPA_TRACE=y additions allows components to register active references
to memory that has been provided to them as a pointer. If such an actively
referenced memory area is freed, tracer will report this as an error and
backtraces of both the invalid free and the location where this pointer
was marked referenced are shown.
|
| |
|
|
|
|
|
|
| |
CONFIG_WPA_TRACE=y and CONFIG_WPA_TRACE_BFD=y can now be used to get
even more complete symbols (func/file/line and inline functions) for
backtraces.
|
| |
|
|
|
|
|
|
|
| |
Use an extra header to move the returned pointer to break os_free()
or free() of the returned value and verify that the correct magic
is present when freeing or resizing the wpabuf. Show backtrace on
invalid wpabuf use.
|
|
|
|
|
| |
This matches with realloc() usage, i.e., allocate a new buffer if no
buffer was specified.
|
|
|
|
|
|
|
|
| |
WPA_TRACE=y builds will now verify that memory allocation in done
consistently using os_{zalloc,malloc,realloc,strdup,free} (i.e., no
mixing of os_* functions and unwrapper functions). In addition, some
common memory allocation issues (double-free, memory leaks, etc.) are
detected automatically.
|
| |
|
| |
|
|
|
|
|
| |
This is not really needed since all signal handlers can use a context
pointer provided during signal handler registration.
|
|
|
|
|
|
|
| |
WPA_TRACE=y can now be used to enable internal backtrace support that
will provide more details about implementation errors, e.g., when some
resources are not released correctly. In addition, this will print out
a backtrace automatically if SIGSEGV is received.
|
| |
|
| |
|
|
|
|
|
|
| |
This allows libeap.a and libeap.so to be built by merging in multiple
libraries from src subdirectories. In addition, this avoids wasting
extra space and time for local builds.
|
|
|
|
|
|
|
|
|
| |
The following defines are not really needed in most places, so
remove them to clean up source code and build scripts:
EAP_TLS_FUNCS
EAP_TLS_OPENSSL
EAP_TLS_GNUTLS
CONFIG_TLS_INTERNAL
|
|
|
|
|
| |
For now, this is hardcoded to support only the internal crypto
implementation.
|
|
|
|
|
| |
This is an initial step on providing an alternative build system that
uses libraries from src subdirectories.
|
| |
|
|
|
|
| |
This removes the only src/crypto dependency from src/utils files.
|
|
|
|
|
| |
Clean up definitions to reduce need to include header files from the
hostapd directory into files under the src subdirectories.
|
|
|
|
|
|
|
|
|
|
|
| |
This is like wpa_msg(), but the output is directed only to
ctrl_interface listeners. In other words, the output will not be
shown on stdout or in syslog.
Change scan result reporting to use wpa_msg_ctrl() for
CTRL-EVENT-SCAN-RESULTS message at info level and wpa_printf() at
debug level to avoid showing scan result events in syslog in the
common configuration used with NetworkManager.
|
|
|
|
|
|
|
|
|
|
| |
gcc 4.4 ends up generating strict-aliasing warnings about some very common
networking socket uses that do not really result in a real problem and
cannot be easily avoided with union-based type-punning due to struct
definitions including another struct in system header files. To avoid having
to fully disable strict-aliasing warnings, provide a mechanism to hide the
typecast from aliasing for now. A cleaner solution will hopefully be found
in the future to handle these cases.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a patch for OpenBSD wired IEEE 802.1X. This is only for wired,
not wireless, because OpenBSD uses wpa_supplicant only on wired now.
http://www.openbsd.org/cgi-bin/cvsweb/ports/security/wpa_supplicant/
I have tested with these.
OS : OpenBSD 4.5
EAP : EAP-TLS
Switch : CentreCOM 8724SL
|
|
|
|
|
|
|
|
|
|
|
| |
If base64_encode() were to be used with a huge data array, the
previous version could have resulted in overwriting the allocated
buffer due to an integer overflow as pointed out in
http://www.freebsd.org/cgi/query-pr.cgi?pr=137484. However, there
are no know use cases in hostapd or wpa_supplicant that would do that.
Anyway, the recommended change looks reasonable and provides additional
protection should the base64_encode() function be used for something
else in the future.
|
|
|
|
|
| |
Instead of using a define and conditional building of md5.c parts,
move the internal-MD5 into a separate file.
|
|
|
|
|
| |
In addition, rename md4.c to md4-internal.c to match in style with
SHA-1 conditionally built internal implementation.
|
|
|
|
|
| |
Instead of using a define and conditional building of sha256.c parts,
move the internal-SHA256 into a separate file.
|
|
|
|
|
| |
In addition, rename aes.c to aes-internal.c to match in style with
SHA-1 conditionally built internal implementation.
|
|
|
|
|
| |
In addition, rename des.c to des-internal.c to match in style with
SHA-1 conditionally built internal implementation.
|
|
|
|
|
| |
Instead of using a define and conditional building of sha1.c parts,
move the internal-SHA-1 into a separate file.
|