-
Notifications
You must be signed in to change notification settings - Fork 11.1k
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
[11.x] Mark sensitive params with SensitiveParameter
attribute
#51940
Conversation
I really like this idea of doing this for anything that could be sensitive. 👍 I'm pretty sure I know you said the PR isn't exhaustive, but I noticed the
I wonder if it would make sense to add this for anywhere the app encryption key is used, in addition to passwords and encryption plaintext? Another spot to check would be the password rehashing code, since from memory it passes around the plaintext too. |
nice catch! I added it to a lot more This should (hopefully) not be a BC break, as the added |
SensitiveParameter
attribute
Hi there, For global attribute we just declare it as |
fixed in d2501a7 |
Since Laravel 11 requires PHP 8.2+, we should make use of the
SensitiveParameter
attribute wherever it makes sense, to prevent potential leaking of sensitive information in logs or stack traces.Is there some special reason, Laravel so far does not use
#[SensitiveParameter]
anywhere?This PR is not feature complete, it's just a start and covers the most crucial spots where we can assume that at least 99.87% of the values are sensitive.