We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Offending code:
How to do it instead:
https://paragonie.com/blog/2015/07/how-safely-generate-random-strings-and-integers-in-php
The text was updated successfully, but these errors were encountered:
Am I missing something here?
The nonce in oauth is more used to prevent the service from processing the same request multiple times and not to prevent some security issue.
Worst case means valid requests will be flagged as invalid.
Without a way for the attacker to use their own new nonce and ability to create a new valid signature with it what good is it to the attacker.
Not arguing it's a suboptimal solution
Sorry, something went wrong.
Nope. I just wanted to call attention to it and suggest using random_int() and bin2hex(random_bytes(16)) respectively.
random_int()
bin2hex(random_bytes(16))
No branches or pull requests
Offending code:
How to do it instead:
https://paragonie.com/blog/2015/07/how-safely-generate-random-strings-and-integers-in-php
The text was updated successfully, but these errors were encountered: