-
Notifications
You must be signed in to change notification settings - Fork 285
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(core-magistrate-crypto): improve 'name' field validation to avoid illegal characters #3148
Conversation
Thanks for submitting this pull request! A maintainer will review this in the next few days and explicitly select labels so you know what's going on. If no reviewer appears after a week, a reminder will be sent out. |
@Lemii could you add some functional tests that ensure that transactions with invalid names get properly rejected and thus not forged? |
@faustbrian Yes, will do. EDIT: Done |
A collaborator has approved this PR. A maintainer will merge this PR shortly. If it shouldn't be merged yet, please leave a comment saying so and we'll wait. Thank you for your contribution! |
Your pull request has been merged and marked as tier 4. It will earn you $20 USD. |
Summary
Closes #3125.
The chosen validation for Business and Bridgechain names is a RegEx that validates for alphanumeric characters, with the addition of a lowercase and dash. This validation has been saved as the 'genericName' schema.
Addtional schemas and validation on the
website
andrepository
fields has intentionally not been created as it's out of scope of this PR (+ ongoing discussion in #3106 ).Checklist