-
Notifications
You must be signed in to change notification settings - Fork 26
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
Require salt in Rfq privateData JSON schema #306
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.
one comment needs addressing but good to go after that ✅
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.
one comment but lgtm
| field | data type | required | description | | ||
| -------- | ------------------------------------------------- | -------- | ------------------------------------------------------------------------------------- | | ||
| `salt` | string | N | | | ||
| `salt` | string | Y | Randomly generated salt used for hashing PrivateData fields | |
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.
nice. the rfq json example below this table will need updating too
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.
this example too actually
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.
good catch. ty
@KendallWeihe pointed out that we should make
salt
a required field inRfq.privateData
because theprivateData
is impossible to validate -- and therefore useless -- without the salt.TODO: validate in at least two implementations: