Skip to content

Commit 3e3813b

Browse files
committed
minor #18730 Add a note about Mock classes not considered for security issues (fabpot)
This PR was merged into the 5.4 branch. Discussion ---------- Add a note about Mock classes not considered for security issues <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/releases for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `6.x` for features of unreleased versions). --> Commits ------- 4a6e6a7 Add a note about Mock classes not considered for security issues
2 parents 010091a + 4a6e6a7 commit 3e3813b

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

contributing/code/security.rst

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,10 @@ email for confirmation):
2121
production (including the web profiler or anything enabled when ``APP_DEBUG``
2222
is set to ``true`` or ``APP_ENV`` set to anything but ``prod``);
2323

24+
* Any security issues found in classes provided to help fo testing that should
25+
never be used in production (like for instance mock classes that contain
26+
``Mock`` in their name);
27+
2428
* Any fix that can be classified as **security hardening** like route
2529
enumeration, login throttling bypasses, denial of service attacks, timing
2630
attacks, or lack of ``SensitiveParameter`` attributes.

0 commit comments

Comments
 (0)