-
Notifications
You must be signed in to change notification settings - Fork 154
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 TLS_PSK_WITH_AES_128_GCM_SHA256 (Philips Hue Entertainment API) #77
Comments
daenney
added a commit
that referenced
this issue
Jul 3, 2019
daenney
added a commit
that referenced
this issue
Jul 3, 2019
daenney
added a commit
that referenced
this issue
Jul 3, 2019
daenney
added a commit
that referenced
this issue
Jul 3, 2019
daenney
added a commit
that referenced
this issue
Jul 4, 2019
daenney
added a commit
that referenced
this issue
Jul 4, 2019
daenney
added a commit
that referenced
this issue
Jul 4, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the same spirit as #45, I'd like to add support for
TLS_PSK_WITH_AES_128_GCM_SHA256
which is what Philips uses for the new Hue Entertainment API.Given we already have PSK support thanks to @Sean-Der's efforts on #45, #76 and we already have AES_128_GCM_SHA256 I suspect this should be relatively straightforward.
I'll take a look at this in the coming weeks, just wanted to file an issue here so it's tracked somewhere.
The text was updated successfully, but these errors were encountered: