Node personalizer sketch seems broken in MySensors 2.3.1
-
Hi,
My node personalizer is running fine as always if I use the 2.3.0 version of the library.
However, when upgrading the library to the latest 2.3.1, it doesn't compile anymore.home/xxx/node-personaliser-signing/node-personaliser-signing.ino: In function 'void write_eeprom_checksum()': node-personaliser-signing:524: error: 'signerSha256Init' was not declared in this scope signerSha256Init(); ^ node-personaliser-signing:526: error: 'signerSha256Update' was not declared in this scope signerSha256Update(buffer, 32); ^ node-personaliser-signing:531: error: 'signerSha256Final' was not declared in this scope hash = signerSha256Final(); ^ exit status 1 'signerSha256Init' was not declared in this scope
Going back to version 2.3.0 overcomes the issue, but I guess it should be solved in 2.3.1, right?
-
-
Bingo! This is a backwards incompatibility
- thanks for reporting!
@joaoabs You should be able to fix this by using the SecurityPersonalizer example from the 2.3.1 lib and copy/paste the settings section from your current sketch to the example sketch.
@Anticimex issue originates from replacing all signerSHA256xyz() functions in the cryptoHAL
3 out of 3
Suggested Topics
-
Code for beta-testing?
Controllers • 24 Mar 2014, 20:48 • andriej 9 Aug 2014, 10:44 -
ESP32 + Signing fails after xxx msg as result of memory leak
Bug Reports • 6 Apr 2020, 18:43 • Technovation 7 Mar 2022, 10:37 -
Missing "__libc_init_array();" wenn using samd without USB
Bug Reports • 6 Jul 2022, 08:36 • ltigges 7 Jul 2022, 22:43 -
Making WiFiManager compatible with MySensors 2.3.2
Bug Reports • 12 Feb 2020, 21:43 • pihome 1 Jun 2022, 16:02 -
Sensor presentation failure
Bug Reports • 31 Jul 2016, 19:23 • Sergio Rius 3 Mar 2021, 18:48 -
some differences between serial- and tcp-gateways.
Bug Reports • 15 Mar 2023, 09:26 • Branther 30 Mar 2023, 15:40