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

Fix manage data value in SEP0010 challenge builder. #396

Merged
merged 2 commits into from
Aug 6, 2019

Conversation

abuiles
Copy link
Contributor

@abuiles abuiles commented Aug 6, 2019

The value must be a 64 byte long base64 encoded
cryptographic-quality random string

We were generating a 64 bytes nonce which wasn't necessarily encoded in base64.

Closes #395

>The value must be a 64 byte long base64 encoded
>cryptographic-quality random string

We were generating a 64 bytes nonce which wasn't necessarily encoded in base64.

Closes #395
Copy link
Member

@ire-and-curses ire-and-curses left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, looks good! I wondered about adding a test for base64 conformance, like this: https://stackoverflow.com/questions/8571501/how-to-check-whether-a-string-is-base64-encoded-or-not

But I don't think it's worth it - we should just trust the encoder ;)

@abuiles
Copy link
Contributor Author

abuiles commented Aug 6, 2019

@ire-and-curses

But I don't think it's worth it - we should just trust the encoder ;)

Agree, I added a test on the verify method, which I think should be good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

SEP 10 implementation of manage data value needs to be base64-encoded
2 participants