Updated 8266 Secure Example #156
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updated ESP8266 Example to include (commented) secure connection options. I have verified insecure (shiftr.io) and fingerprint (SHA1, my personal site) functions work 100%. I have verified that the KEY and CERT functions can pull/authenticate, but do not have a full MQTT site to test complete functionality (should work, similar to SHA1).
Updating to include secure functions
Add updated secure functions
…uzzahESP8266Secure/AdafruitHuzzahESP8266Secure.ino
|
Closing pull request, as the version update notes secure connection comment/example has been updated. Maybe leave this archived for a reference sha1 example |
|
Sorry, for not considering this. It would be nice if you could add the example to the wiki. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated ESP8266 Example to include (commented) secure connection options. I have verified insecure (shiftr.io) and fingerprint (SHA1, my personal site) functions work 100%. I have verified that the KEY and CERT functions can pull/authenticate, but do not have a full MQTT site to test complete functionality (should work, similar to SHA1).
See the comments throughout code for details - to get the secure functions to work, some lines need to be commented/un-commented.