Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

mesh creator needs frequency #1

Open
twpedersen opened this issue May 21, 2013 · 0 comments
Open

mesh creator needs frequency #1

twpedersen opened this issue May 21, 2013 · 0 comments

Comments

@twpedersen
Copy link
Member

a frequency must be specified in the mesh network block, otherwise the nl80211 bss->freq will be 0, even though wpa_s chooses a channel for us.
chunyeow referenced this issue Jun 5, 2013
@chunyeow
mesh: move the SAE state earlier
52987c3 
Perhaps, due to reception of SAE frame from another peer while
in SAE_NOTHING state.

This seems to solve the following segmentation fault:

authentication: STA=00:1b:b1:07:9a:2b auth_alg=3 auth_transaction=2 status_code=0 wep=0
hostapd_logger: STA 00:1b:b1:07:9a:2b - SAE confirm before commit
hostapd_logger: STA 00:1b:b1:07:9a:2b - SAE authentication (RX confirm)
SAE: peer-send-confirm 0

Program received signal SIGSEGV, Segmentation fault.
0xb7e48eb7 in EC_POINT_get_affine_coordinates_GFp () from /lib/i386-linux-gnu/libcrypto.so.1.0.0
(gdb)
(gdb) bt
      at ../src/crypto/crypto_openssl.c:1133
      element2=0x8114208, confirm=0xbfffed3c "\200\376\020\b\204\355\377\277") at ../src/common/sae.c:940
      at ../src/ap/ieee802_11.c:524
      at ../src/drivers/driver_nl80211.c:1334
      ack=0x0, cookie=0x0, sig=0x8112754) at ../src/drivers/driver_nl80211.c:1518
      at ../src/drivers/driver_nl80211.c:2438

Signed-off-by: Chun-Yeow Yeoh <[email protected]>
bcopeland pushed a commit that referenced this issue Jul 14, 2014
@jmalinen
PKCS #1: Allow only BT=01 for signature in internal TLS
e6d83cc 
Based on PKCS #1, v1.5, 10.1.3, the block type shall be 01 for a
signature. This avoids a potential attack vector for internal TLS/X.509
implementation.

Signed-off-by: Jouni Malinen <[email protected]>
bcopeland pushed a commit that referenced this issue Jul 14, 2014
@jmalinen
PKCS #1: Enforce minimum padding for decryption in internal TLS
6c5be11 
Follow the PKCS #1 v1.5, 8.1 constraint of at least eight octets long PS
for the case where the internal TLS implementation decrypts PKCS #1
formatted data. Similar limit was already in place for signature
validation, but not for this decryption routine.

Signed-off-by: Jouni Malinen <[email protected]>
bcopeland pushed a commit that referenced this issue Jul 14, 2014
@jmalinen
tests: Add CAVP test vectors for RSA/PKCS #1 v1.5 signature validation
46fcf47 
This allow the PKCS #1 and RSA implementation to be validated against
the test vectors from
http://csrc.nist.gov/groups/STM/cavp/documents/dss/186-2rsatestvectors.zip
and
http://csrc.nist.gov/groups/STM/cavp/documents/dss/SigVer15EMTest.txt.

Signed-off-by: Jouni Malinen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@twpedersen