@@ -44,7 +44,7 @@ This is hosted by a webserver and contains information about the latest firmware
44
44
"version" : 2 ,
45
45
"host" : " 192.168.0.100" ,
46
46
"port" : 80 ,
47
- "bin" : " /fota/esp32-fota-http-2.bin" ,
47
+ "bin" : " /fota/esp32-fota-http-2.bin"
48
48
}
49
49
```
50
50
@@ -54,7 +54,7 @@ Version information can be either a single number or a semantic version string.
54
54
{
55
55
"type" : " esp32-fota-http" ,
56
56
"version" : " 2.5.1" ,
57
- "url" : " http://192.168.0.100/fota/esp32-fota-http-2.bin" ,
57
+ "url" : " http://192.168.0.100/fota/esp32-fota-http-2.bin"
58
58
}
59
59
```
60
60
@@ -65,7 +65,7 @@ A single JSON file can provide information on multiple firmware types by combini
65
65
{
66
66
"type" :" esp32-fota-http" ,
67
67
"version" :" 0.0.2" ,
68
- "url" :" http://192.168.0.100/fota/esp32-fota-http-2.bin" ,
68
+ "url" :" http://192.168.0.100/fota/esp32-fota-http-2.bin"
69
69
},
70
70
{
71
71
"type" :" esp32-other-hardware" ,
@@ -140,7 +140,7 @@ void loop()
140
140
You can now sign your firmware image with an RSA public/private key pair and have the ESP32 check if the signature is correct before
141
141
it switches over to the new image.
142
142
143
- In order to use this feature, enable `check_signature` in `firmware.json` . Next create a key-pair to sign your firmware image:
143
+ In order to use this feature just set the boolean `validate` to `true` in the constructor . Next create a key-pair to sign your firmware image:
144
144
```
145
145
openssl genrsa -out priv_key.pem 4096
146
146
openssl rsa -in priv_key.pem -pubout > rsa_key.pub
@@ -176,4 +176,4 @@ This relies on [semver.c by h2non](https://github.com/h2non/semver.c) for semant
176
176
* @nuclearcat
177
177
* @thinksilicon
178
178
* @nuclearcat
179
- * @hpsaturn
179
+ * @hpsaturn
0 commit comments