/hostap-3.6.0/src/crypto/ |
D | crypto_wolfssl.c | 1454 ecc_point *point = (ecc_point *) p; in crypto_ec_point_deinit() local 1460 mp_forcezero(point->x); in crypto_ec_point_deinit() 1461 mp_forcezero(point->y); in crypto_ec_point_deinit() 1462 mp_forcezero(point->z); in crypto_ec_point_deinit() 1464 wc_ecc_del_point(point); in crypto_ec_point_deinit() 1476 const struct crypto_ec_point *point, u8 *x, u8 *y) in crypto_ec_point_to_bin() argument 1478 ecc_point *p = (ecc_point *) point; in crypto_ec_point_to_bin() 1509 ecc_point *point = NULL; in crypto_ec_point_from_bin() local 1515 point = wc_ecc_new_point(); in crypto_ec_point_from_bin() 1516 if (!point) in crypto_ec_point_from_bin() [all …]
|
D | crypto_openssl.c | 1858 const struct crypto_ec_point *point, u8 *x, u8 *y) in crypto_ec_point_to_bin() argument 1871 EC_POINT_get_affine_coordinates_GFp(e->group, (EC_POINT *) point, in crypto_ec_point_to_bin() 2346 EC_POINT *point = NULL; in crypto_ec_key_set_pub() local 2369 point = EC_POINT_new(ec_group); in crypto_ec_key_set_pub() 2370 if (!x || !y || !point) in crypto_ec_key_set_pub() 2373 if (!EC_POINT_set_affine_coordinates_GFp(ec_group, point, x, y, ctx)) { in crypto_ec_key_set_pub() 2380 if (!EC_POINT_is_on_curve(ec_group, point, ctx) || in crypto_ec_key_set_pub() 2381 EC_POINT_is_at_infinity(ec_group, point)) { in crypto_ec_key_set_pub() 2389 EC_KEY_set_public_key(eckey, point) != 1) { in crypto_ec_key_set_pub() 2407 EC_POINT_free(point); in crypto_ec_key_set_pub() [all …]
|
D | crypto.h | 838 const struct crypto_ec_point *point, u8 *x, u8 *y);
|
/hostap-3.6.0/doc/ |
D | porting.doxygen | 60 \ref config_none.c can be used as an empty starting point for building a 136 \section entry_point Program entry point 144 \ref wpa_supplicant/main.c includes an entry point for UNIX-like 147 operating systems, similar OS-specific entry point implementation is 153 \ref wpa_supplicant_i.h. In most cases, the entry point function should 188 include a driver interface. However, this is a good starting point 194 made functional by adding a proper program entry point (main*.c),
|
D | testing_tools.doxygen | 21 integrates IEEE 802.1X Authenticator (normally, an access point) and 24 having to setup an access point and a wireless client. 90 access point.
|
D | mainpage.doxygen | 63 hostapd includes IEEE 802.11 access point management (authentication /
|
D | p2p.doxygen | 252 provisioning step at this point by configuring WPS Registrar or 259 state at this point and allows new group formation attempts to be 267 group formation state at this point and allows new group formation
|
D | dbus.doxygen | 265 <dd>A passed path doesn't point to any network object.</dd> 267 <dd>A passed path doesn't point to any network object.</dd> 289 <dd>A passed path doesn't point to any network object.</dd> 291 <dd>A passed path doesn't point to any network object.</dd> 605 <dd>A passed path doesn't point to any network object.</dd> 607 <dd>A passed path doesn't point to any network object.</dd>
|
/hostap-3.6.0/hostapd/ |
D | README-WPS | 14 passphrase/PSK) and configuration of an access point and client 28 - access point: the WLAN access point 37 when WPS is used to configure the access point. 51 point, e.g., for initial network setup. In addition, hostapd can proxy a 88 # empty file as a starting point). 197 negotiation. At that point, a new, random WPA PSK is generated for the 210 At this point, the client has two minutes to complete WPS negotiation
|
D | README-MULTI-AP | 36 From the point of view of hostapd, there is nothing special about these 40 links. A backhaul link is a link between two access point devices, giving 41 internet access to access point devices that don't have a wired link. The 94 hostapd on AP). Note that point 1 means that hostapd must not be configured
|
D | README | 111 Server. An access point includes an Authenticator that relays the packets 148 When a station would like to use the services of an access point, it 154 point. The Authenticator will then ask the Supplicant to authenticate
|
D | android.config | 22 # newer libnl version and point the hostapd build to use it.
|
D | defconfig | 25 # you may need to point hostapd to your version of libnl.
|
D | ChangeLog | 1157 updated at this point and if there was a pending message with long
|
/hostap-3.6.0/wpa_supplicant/ |
D | README-WPS | 15 passphrase/PSK) and configuration of an access point and client 29 - access point: the WLAN access point 38 when WPS is used to configure the access point. 117 entered at the Registrar to complete WPS registration. At that point, 153 At this point, the AP/Registrar has two minutes to complete WPS
|
D | README-Windows.txt | 52 starting point for building the programs with VS2005 IDE. Visual Studio 299 starting point for the configuration.
|
D | defconfig | 38 # you may need to point hostapd to your version of libnl. 272 # Select program entry point implementation:
|
D | eap_testing.txt | 379 terminate at this point (gets somewhat confused with reply to this)
|
D | android.config | 235 # Select program entry point implementation:
|
D | README | 907 # At this point, the new network interface should start trying to associate
|
D | ChangeLog | 1842 Windows registry and with the entry point designed to run as a 1856 avoid confusing reports of old errors being reported at later point
|
/hostap-3.6.0/wpa_supplicant/doc/docbook/ |
D | eapol_test.sgml | 53 access point) and IEEE 802.1X Supplicant (normally, a wireless 55 test EAP methods without having to setup an access point and a
|
D | wpa_supplicant.sgml | 693 <!-- XXX at this point, the page could include a little script
|
/hostap-3.6.0/tests/hwsim/ |
D | README | 192 modify and add new test cases. The easiest starting point for this is
|