Searched refs:secure (Results 1 – 15 of 15) sorted by relevance
| /hostap-latest/tests/hwsim/ |
| D | test_wpas_mesh.py | 24 def check_mesh_support(dev, secure=False): argument 27 if secure: 398 check_mesh_support(dev[0], secure=True) 418 check_mesh_support(dev[0], secure=True) 431 check_mesh_support(dev[0], secure=True) 444 check_mesh_support(dev[0], secure=True) 456 check_mesh_support(dev[0], secure=True) 491 check_mesh_support(dev[0], secure=True) 517 check_mesh_support(dev[0], secure=True) 537 check_mesh_support(dev[0], secure=True) [all …]
|
| /hostap-latest/hostapd/ |
| D | defconfig | 93 # EAP-pwd for the integrated EAP server (secure authentication with a password) 254 # secure than using the same sequence of random numbers after every reboot. 267 # yet secure randomness source than /dev/random on Linux 3.17 and newer. 399 # considered secure. It should not be used for anything anymore. The 407 # considered secure. It should not be used anymore. For now, the default hostapd
|
| D | README-WPS | 22 not very secure. As such, use of WPS may not be suitable for 23 environments that require secure network access without chance for 218 secure option is to use hostapd_cli wps_ap_pin command to enable the
|
| D | android.config | 213 # considered secure. It should not be used for anything anymore. The
|
| D | ChangeLog | 23 * extend PASN support for secure ranging
|
| /hostap-latest/wpa_supplicant/ |
| D | defconfig | 142 # EAP-pwd (secure authentication using only a password) 485 # much more secure than using the same sequence of random numbers after every 498 # yet secure randomness source than /dev/random on Linux 3.17 and newer. 654 # considered secure. It should not be used for anything anymore. The 662 # considered secure. It should not be used anymore for anything else than a
|
| D | android.config | 108 # EAP-pwd (secure authentication using only a password) 423 # much more secure than using the same sequence of random numbers after every 539 # considered secure. It should not be used for anything anymore. The
|
| D | README-DPP | 13 enrolling of interface-less devices in a secure Wi-Fi network using many
|
| D | README-WPS | 23 not very secure. As such, use of WPS may not be suitable for 24 environments that require secure network access without chance for
|
| D | README-HS20 | 567 pairwise_cipher (CCMP = secure, NONE = no encryption used).
|
| D | ChangeLog | 29 - extend support for secure ranging 309 - note: these changes are not fully backwards compatible for secure
|
| /hostap-latest/src/ap/ |
| D | wpa_auth.c | 4664 int secure, gtkidx, encr = 0; local 4790 secure = 1; 4808 secure = 0; 4825 secure = 1; 5002 (secure ? WPA_KEY_INFO_SECURE : 0) | 7048 int wpa_ie_len, secure, gtkidx, encr = 0; local 7075 secure = 1; 7083 secure = 0; 7099 secure = 1; 7207 (secure ? WPA_KEY_INFO_SECURE : 0) |
|
| /hostap-latest/hs20/server/ |
| D | hs20-osu-server.txt | 12 secure to be installed in a publicly available Internet server without
|
| /hostap-latest/wpa_supplicant/doc/docbook/ |
| D | wpa_supplicant.sgml | 46 secure. IEEE 802.1X authentication and frequently changed dynamic WEP keys 52 cryptographic algorithm AES) can finally be called secure and used for
|
| /hostap-latest/src/rsn_supp/ |
| D | wpa.c | 1165 const u8 *addr, int secure) in wpa_supplicant_key_neg_complete() argument 1175 if (secure) { in wpa_supplicant_key_neg_complete()
|