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

[internal] [photon/p1] crypto: re-enables MD5 for TLS (WPA Enterprise) #1743

Merged
merged 1 commit into from
Apr 4, 2019

Conversation

avtolstoy
Copy link
Member

@avtolstoy avtolstoy commented Apr 4, 2019

Problem

MD5 got erroneously disabled for Photon and P1 during the development of 1.1.0-rc.1, which prevents WPA Enterprise authentication not working correctly.

Solution

Bring it back!

Steps to Test

Connect to WPA Enterprise AP with PEAP. Your device shouldn't crash.

Example App

N/A

References

N/A


Completeness

  • User is totes amazing for contributing!
  • Contributor has signed CLA (Info here)
  • Problem and Solution clearly stated
  • Run unit/integration/application tests on device
  • Added documentation
  • Added to CHANGELOG.md after merging (add links to docs and issues)

  • [internal] [photon/p1] crypto: re-enables MD5 for TLS (WPA Enterprise) #1743

@avtolstoy avtolstoy added this to the 1.1.0-rc.1 milestone Apr 4, 2019
@avtolstoy avtolstoy requested a review from technobly April 4, 2019 14:06
@technobly technobly added bug ready to merge PR has been reviewed and tested and removed needs review labels Apr 4, 2019
@technobly technobly merged commit 8118508 into develop Apr 4, 2019
@technobly technobly deleted the fix/photon-p1-wpa-ent-md5 branch April 4, 2019 20:21
@technobly technobly changed the title [photon/p1] crypto: re-enables MD5 for TLS (WPA Enterprise) [internal] [photon/p1] crypto: re-enables MD5 for TLS (WPA Enterprise) Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug internal ready to merge PR has been reviewed and tested
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants