We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The advertisement of the public key should be implemented in a different way as not all hard-/software supports this feature.
For example Apple does not allow to send the MFData using the CoreBluetooth service https://developer.apple.com/documentation/corebluetooth/cbperipheralmanager/1393252-startadvertising
advertisementData An optional dictionary containing the data you want to advertise. The peripheral manager only supports two keys: CBAdvertisementDataLocalNameKey and CBAdvertisementDataServiceUUIDsKey.
What about adding a read functionality to the the identify characteristic and sending the full 32 bytes of the verifier public key over this channel?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The advertisement of the public key should be implemented in a different way as not all hard-/software supports this feature.
For example Apple does not allow to send the MFData using the CoreBluetooth service
https://developer.apple.com/documentation/corebluetooth/cbperipheralmanager/1393252-startadvertising
What about adding a read functionality to the the identify characteristic and sending the full 32 bytes of the verifier public key over this channel?
The text was updated successfully, but these errors were encountered: