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.

Sign up for GitHub

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

Jump to bottom

Define normalization algorithm for header data to be used in conditions #56

Closed
adrianhopebailie opened this issue Jul 17, 2016 · 2 comments
Closed

Define normalization algorithm for header data to be used in conditions #56

adrianhopebailie opened this issue Jul 17, 2016 · 2 comments

Comments

@adrianhopebailie
Copy link
Collaborator

From: #54 (comment)

To use header data in the condition it must be normalized before it is signed/hashed. The algorithm for this needs to be standardized so it is repeatable and deterministic.
@emschwartz
Copy link
Member

To be more precise, the ASN.1 SEQUENCE types already define the ordering of the fields within a given header. I think what you're saying is that we should have a recommended ordering for the different headers attached to a packet (see IPv6)

@adrianhopebailie
Copy link
Collaborator Author

Yes. If the data that is being signed includes multiple headers (ILP + ITP for example) then we need to define how to normalize the combined data

@emschwartz emschwartz mentioned this issue Aug 16, 2016
Merged
emschwartz added a commit that referenced this issue Aug 16, 2016
@emschwartz
docs(0011): itp -> interledger payment request (ipr)
7084edc 
closes #66, closes
#68, closes
#56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@adrianhopebailie @emschwartz