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.
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
Add missing KeyMgmt caps #4
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this I'm still getting the warning on sae.
Looks like there's another mapping in gsupplicant.c. Wonder why there are two of those.
Hmm, do you have a backtrace? |
Not sure does the backtrace matter much when the warning source is known, but since you asked added a breakpoint there: Thread 1 "connmand" hit Breakpoint 1, gsupplicant_parse_bits_array (mask=0, count=3, map=0xb6b9b8ec <keymgmt_map>, value=0xbea9d950, name=0xb604b490 "KeyMgmt") at src/gsupplicant_util.c:187 |
Ah, it's parsing bss rather than interface caps. Thanks, will update the PR. |
Looking more closely gsupplicant_bss_parse_wpa from the backtrace, looks like there's a third (!) mapping on gsupplicant_bss.c:484 |
Right. There are three |
I have decided to use the same mapping for all cases. Does that fix the problem? |
And reuse |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now the sae warning is gone, but this one getting printed a lot:
[gsupplicant] WARNING! Unexpected Group value
I have to admit that I didn't test the changes on a real device 😐 Will do. |
Now it should become silent |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems good now. Thanks.
That should silence KeyMgmt SAE not known warning