-
Notifications
You must be signed in to change notification settings - Fork 70
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
fix(packet): add precheck for timestamps in Prepares #707
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good!
Could do a git rebase --signoff
onto the repos master branch?
2a89cc4
to
5e5c8c1
Compare
…rono Signed-off-by: bwty <whalelephant@users.noreply.github.com> test: datetime ensure error with invalid characters Signed-off-by: bwty <whalelephant@users.noreply.github.com> doc: Prepare package datetime spec Signed-off-by: bwty <whalelephant@users.noreply.github.com> Signed-off-by: bwty <whalelephant@users.noreply.github.com>
Signed-off-by: bwty <whalelephant@users.noreply.github.com>
Signed-off-by: bwty <whalelephant@users.noreply.github.com>
Signed-off-by: bwty <whalelephant@users.noreply.github.com>
bb3c289
to
a47ac32
Compare
Signed-off-by: bwty <whalelephant@users.noreply.github.com>
a47ac32
to
b0e9b99
Compare
This is a correctness update which will deny some patterns which were previously accepted as valid timestamps, but did not adhere to RFC and the asn1 specification. The previously accepted timestamps can be seen with the test case. Merging slightly ahead of the 24h window. |
this follows from finding a case where the parsed timestamp doesn't match the output timestamp, even with the fix made in interledger#707. the strict feature is included in the "rountrip-only". Signed-off-by: Joonas Koivunen <joonas.koivunen@gmail.com>
Cc: #705
Check if bytes are numerical values before handing to chrono