- Fix UDP send
- Add a default value for MY_IP_GATEWAY_ADDRESS and
MY_IP_SUBNET_ADDRESS, making them optional when using MY_IP_ADDRESS
- Add support for MY_IP_GATEWAY_ADDRESS and MY_IP_SUBNET_ADDRESS to
W5100
* Signing support with MAX_PAYLOAD>32
Support in the signing backends to handle configurations
where MAX_PAYLOAD is more than 32 bytes.
Fixes#748
* Support big message signatures
Support for signing messages larger than 32 bytes.
This is not fully testable with the current version of
the library but the change would add theoretical support
for signing any sized messages.
Fixes#749
* Have gw properly indicate whitelisting preferences
If the gateway hold a signing whitelist, inform all
nodes of this requirement and not just nodes that hold
whitelists themselves.
Fixes#806
* Harden security
The flag MY_SIGNING_GW_REQUEST_SIGNATURES_FROM_ALL
has been removed. Gateway will now request signatures
from everyone by default.
In addition to this, no nodes in the network will allow
clearing of signing/whitelisting preferences by OTA
commands by default.
If the old behaviour is needed (suitable for gradual
signing roll out and development purposes) a new flag,
MY_SIGNING_WEAK_SECURITY can be set.
Fixes#807
* Signing debug messages rewritten
All signing related debug has been rewritten to
better match other core debug printouts.
Also, backends are updated to have a smaller
implementation delta.
* Simplified signing option implemented
Enable by MY_SIGNING_SIMPLE_PASSWD. Signing, and signing requirements
will be enabled, as will encryption. Whitelisting is optional.
The value provided to MY_SIGNING_SIMPLE_PASSWD is used as HMAC and AES
key. Whitelists use the first 8 bytes of the password and the ninth
byte from the node ID as serial.
Password is required to be at least 8 characters wide. It is zero
padded if it is not long enough to cover the AES (16 bytes) and HMAC
(32 bytes) keys. It is not recommended to have a password shorter than
32 bytes, and there is no need for a password longer than 32 bytes.
* Add documentation section for signing debug
* Add nRF5 encryption to simple signing option
* Restructure MySigning documentation
* Minor fixes for Linux
This commit changes the way random numbers are available
with MySensors.
The AVR platform uses a 32 Bit random seed build from a floating
analog pin. The way of the generation of this seed is FIPS 140-2
compliant.
For support MCU with a fast way to generate random data, the
hwGetentropy() command is now available to allow rapid generation
of random data.
The ESP8266 platform uses the internal random source for randomness
for hwGetentropy() and Arduino's random() function.
The NRF5 platform initializes the pseudo random number generator
from internal hardware number generator. The internal AES-ECB unit
generates random data after filling with HWRNG data by AES-CBC.
On Linux getrandom() is implemented via syscall().
signerAtsha204SoftGetNonce speed:
AVR = ~14000us (sha204Soft)
NRF51 = ~152us (AES-CBC), 1739us (old sha204Soft)
NRF52 = ~31us (AES-CBC), 183us (old sha204Soft)
ESP8266 = ~20us (RANDOM_REG32), 380us (old sha204Soft)
All Nonce results tested for FIPS 140-2 compliance successfully.
* Removed ability to lock data section
* Introduced "guided mode" to simplify process
* Refactored the sketch to be less monolithic
* Print details and instructions in tables
* Use device unique ID as serial when
* Calculate and store personalization checksum
* Print serial in a copy+paste friendly manner (fixes#804)
* Clarify meaning of UART confirmation (fixes#805)
Removing MY_LED_BLINKING_FEATURE, as we now are
using MY_DEFAULT_LED_xx_PIN defines to enable
LED blinking feature.
updated Gateway sketches to not refer to
MY_LED_BLINKING_FEATURE any more
fixes#562
tekka
Mikael Falkvidd
d00616
Patrick Fallberg
Marcelo Aquino
Frédéric FRANCE
FotoFieber
Marcelo Aquino
Thomas Mørch
petewill
Henrik Ekblad
Tom
Thomas Mørch
Mikael Falkvidd git@mjo.se
Shiny