Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update signing backends to handle a MAX_PAYLOAD of 32 bytes or more #748

Closed
fallberg opened this issue Jan 18, 2017 · 0 comments
Closed

Comments

@fallberg
Copy link
Contributor

The signing backends will fail, crash, do horrible things, if MAX_PAYLOAD is 32 bytes or more. It is actually a desirable thing to have a MAX_PAYLOAD larger than 32 bytes as that implies the ability to exchange max size nones and non-truncated signatures.

@fallberg fallberg self-assigned this Jan 18, 2017
@fallberg fallberg added this to the 2.2.0 milestone Jan 18, 2017
fallberg added a commit to fallberg/MySensors that referenced this issue Jan 18, 2017
Support in the signing backends to handle configurations
where MAX_PAYLOAD is more than 32 bytes.

Fixes mysensors#748
fallberg added a commit to fallberg/MySensors that referenced this issue Apr 2, 2017
Support in the signing backends to handle configurations
where MAX_PAYLOAD is more than 32 bytes.

Fixes mysensors#748
fallberg added a commit to fallberg/MySensors that referenced this issue May 12, 2017
Support in the signing backends to handle configurations
where MAX_PAYLOAD is more than 32 bytes.

Fixes mysensors#748
fallberg added a commit to fallberg/MySensors that referenced this issue May 26, 2017
Support in the signing backends to handle configurations
where MAX_PAYLOAD is more than 32 bytes.

Fixes mysensors#748
fallberg added a commit to fallberg/MySensors that referenced this issue May 29, 2017
Support in the signing backends to handle configurations
where MAX_PAYLOAD is more than 32 bytes.

Fixes mysensors#748
@fallberg fallberg moved this from In progress to Merged in 2.3.1 Nov 12, 2017
@fallberg fallberg removed this from Done/merged in 2.3.1 Feb 25, 2018
@fallberg fallberg removed this from the 2.2.0 milestone Feb 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant