Force SPIFFS Update and custom key length #132
Merged
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.
I've added the function forceUpdateSPIFFS with the same logic of forceUpdate to have the possibility to update the SPIFFS without json from a custum url, i've added a new function for the OTA execution because with execOTA after the spiffs update the code was trying also to download a new firmware.
I've also added the length of the signature key to use the same key that is used in some esp8266 system that have a key length limitation. To to that i've added a member to store the key lenght that at default is 512 as before. The signature variable now is dynamic allocated to manage the different size.
I've made and test this code to force the update of a esp32 from a URL that is coming from mqtt.