Closed matt2112 closed 4 years ago
Hi I ma not the project manager of this project.
You can contact the pm directly.
Cordialement/Regards/Mit freundlichen Grüßen/Cordiali saluti/Saludos/تحية خالصة
Azzedine Ramrami
OWASP Morocco Chapter
OWASP AppSec Africa President
IBM Security - Senior Security & Network Architect Data & Application Security, Cogntive Security, IoT/OT/ICS/SCADA Security & SIEM Certified Mile2 CPTE/CPTC/CDFE/CSWAE and EC-Council C|EH
OWASP Morocco Leader/OWASP AppSec Africa President
IBM Security Global Speaker
Consider giving back, and supporting the open source community by becoming a member or making a donation today!
Join us at AppSec Morocco & Africa 2020 June 4 & 5 Rabat/Morocco!
Phone: +33 1 58 75 18 17 | Mobile: +33 6 65 48 90 04 / +33 6 10 25 93 15 E-mail: azzeddine.ramrami@owasp.org azzeddine.ramrami@gmail.com
Le mar. 18 août 2020 à 08:41, Matt Lewis notifications@github.com a écrit :
Noticed a pretty confusing typo when reading the 2017 spec for Broken Authentication, assuming I haven't dramatically misunderstood its intention!
Also have a PR in www-project-top-ten https://github.com/OWASP/www-project-top-ten/pull/24 and Top10 https://github.com/OWASP/Top10/pull/507.
You can view, comment on, or merge this pull request online at:
https://github.com/OWASP/RiskAssessmentFramework/pull/60 Commit Summary
- Fix typo in broken authentication
File Changes
- M gui/src/app/view/resources/resources.component.ts https://github.com/OWASP/RiskAssessmentFramework/pull/60/files#diff-f7e0fb0c9d6ff6e6ca539bafd4a836f1 (2)
Patch Links:
- https://github.com/OWASP/RiskAssessmentFramework/pull/60.patch
- https://github.com/OWASP/RiskAssessmentFramework/pull/60.diff
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/OWASP/RiskAssessmentFramework/pull/60, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABXCECH6BQIN7CMCAMMUELSBIWCPANCNFSM4QC7M3KA .
I believe this is not a typo, see https://github.com/OWASP/Top10/pull/507#issuecomment-676486700 for my reasoning.
Noticed a pretty confusing typo when reading the 2017 spec for Broken Authentication, assuming I haven't dramatically misunderstood its intention!
Also have PRs for the same issue in www-project-top-ten and Top10.