Skip to content

Commit 765af8d

Browse files
codedustturt2live
andauthored
Proposal template: explicitly mention RFC 3552 in security section (#4378)
* Template: explicitly mention RFC 3552 in security section Signed-off-by: codedust <codedust@users.noreply.github.com> * Apply suggestions from code review --------- Signed-off-by: codedust <codedust@users.noreply.github.com> Co-authored-by: Travis Ralston <travpc@gmail.com>
1 parent b8a558a commit 765af8d

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

proposals/0000-proposal-template.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,8 @@ idea.
8787

8888
**All proposals must now have this section, even if it is to say there are no security issues.**
8989

90-
*Think about how to attack your proposal, using lists from sources like
90+
*Think about how to attack your proposal. See [RFC 3552](https://datatracker.ietf.org/doc/html/rfc3552)
91+
for things to think about, but in particular pay attention to lists from sources like
9192
[OWASP Top Ten](https://owasp.org/www-project-top-ten/) for inspiration.*
9293

9394
*Some proposals may have some security aspect to them that was addressed in the proposed solution. This

0 commit comments

Comments
 (0)