Document the new security:check command #4051
Labels
hasPR
A Pull Request has already been submitted for this issue.
Comments
|
I think it'll be nice if we have a small |
|
If I remember correctly, we have some places where we describe a change in the behaviour due to security fixes (at least the maximum number of iterations in the password encoder). I think it makes sense to link to the security checker and introduce the |
weaverryan
added a commit
that referenced
this issue
Jan 1, 2015
This PR was merged into the 2.3 branch. Discussion ---------- Documented the security:check command | Q | A | ------------- | --- | Doc fix? | no | New docs? | yes | Applies to | all | Fixed tickets | #4051 Commits ------- 897dc70 Added a lot of changes suggested by reviewers fdfb1a0 Added a note about the SensioDistributionBundle necessary for security:check 3c9a962 Added a note about the security:check command e552369 Added a missing link reference 0e7d0cd Added a note about the security advisories database 36d3f2b This command is available sin Symfony 2.5 7f3fb71 Documented the security:check command
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symfony 2.6 will include a new
security:checkcommand to check your dependencies for the known security vulnerabilities: sensiolabs/SensioDistributionBundle#149Should we include a reference of this command where appropriate in the Book or Cookbook? Should we include it just in the bundle's documentation?
The text was updated successfully, but these errors were encountered: