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.

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

Support deauthentication codes #349

Merged
merged 4 commits into from
Oct 17, 2020

Conversation

usr-sse2
Copy link
Contributor

@usr-sse2 usr-sse2 commented Oct 15, 2020

Pass through deauthentication codes to getDEAUTH and setLinkStatus, so that airportd knows the deauthentication reason and whether it is voluntary (because of setDISASSOCIATE) or caused by AP.
Add noise information in scan results.
Log unhandled set requests when only get is implemented or vice versa.

@usr-sse2 usr-sse2 changed the title Status and rssi Support deauthentication codes Oct 15, 2020
@usr-sse2 usr-sse2 marked this pull request as ready for review October 15, 2020 09:33
@zxystd zxystd self-requested a review October 15, 2020 09:43
@usr-sse2 usr-sse2 marked this pull request as draft October 15, 2020 10:10
@usr-sse2
Copy link
Contributor Author

Oops, build failed with latest changes.

@usr-sse2 usr-sse2 marked this pull request as ready for review October 15, 2020 10:51
cd->capabilities[5] = 0x80;//isCntryDefaultSupported
cd->capabilities[5] |= 0x0C;
cd->capabilities[6] = 0x8D;
cd->capabilities[7] = 0x84; // This byte contains Apple Watch unlock
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I checked that bytes 0, 1 and 7 alone are sufficient for Apple Watch unlock. It can only unlock administrative permissions and doesn't try to unlock the lock screen, because AWDL capability is disabled (something in bytes 2-6). If these bytes are set, then it tries to unlock the lock screen too but fails, because AWDL features are not implemented.
Besides, here is an open implementation of AWDL protocol that can be used for reference: https://owlink.org/code/

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree with you, but I think we should keep this flags on, because we don't know whether these flags will affect other functionalities, the best way is to keep them in dev state. right? also, I think we can comment this for further use(not deleted).

Copy link
Contributor Author

@usr-sse2 usr-sse2 Oct 15, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that bytes 2-6 should be left on, except bits for ARP and NDP offload (we have to find out which bits are they). As bytes 8-9 currently don't seem to enable anything useful, they can be commented out.

@williambj1 williambj1 added the enhancement New feature or request label Oct 15, 2020
memset(hv, 0, sizeof(*hv));
hv->version = APPLE80211_VERSION;
hv->status = APPLE80211_STATUS_SUCCESS;
hv->status = ic->ic_assoc_status;
XYLog("%s, %d\n", __FUNCTION__, hv->status);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this log should be remove, it will be called for several times when associating.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, can be removed or replaced with a DPRINTF. It was left from debugging.

@zxystd zxystd merged commit 0028810 into OpenIntelWireless:master Oct 17, 2020
daimali666 pushed a commit to daimali666/itlwm that referenced this pull request Oct 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

Successfully merging this pull request may close these issues.

3 participants