-
-
Notifications
You must be signed in to change notification settings - Fork 394
Various recommendations #23
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
Conversation
DSotnikov
commented
Sep 23, 2019
- Added various How To Prevent recommendations to A3, A4, A6, A7, A8, A9.
- Added a scenario of admin level gained by a parameter change in A5 exploit scenario.
- Added APISecurity.io as education resource in What's Next for Developers.
- Changed the git repo clone URL in contributing.md.
v0.1.1 * New educational materials for Developers
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.
Hi @DSotnikov,
Thanks for your contribution.
I had the chance to review your PR.
Please check my comments.
If you agree with my comments I can do the required changes and merge your PR.
As per the CONTRIBUTING.md, Pull Requests should be opened to the develop
branch.
I can solve this locally, adding your suggestions to the develop
branch. They should be released very soon.
Cheers,
Paulo A. Silva
Thanks, @PauloASilva, most changes you propose are great. A3 is the only one in which I think my original suggestion was hard to understand and so the meaning got lost. See my new proposal. And yes, feel free to make the changes and merge the PR as appropriate. Thanks a lot for your help and your work on the project! |
Hi @DSotnikov, Thanks for contributing, |