Reputation: 6184
Django has some nice helpers for ensuring sensitive data (passwords, credit card data) never gets reflected in logs or error output. This functionality is also available in some third-party tools like Raygun
Is there a built-in equivalent for Laravel?
For example, error pages and presumably debug emails include the complete raw POST data; I would like to strip this out.
One approach is to remove keys from $_POST
after reading from it, but is this enough to prevent accidental password exposure?
Upvotes: 1
Views: 1222
Reputation: 11943
No, there is not.
If you're debugging something then it definitely makes sense for debug mode to show you what's going on and to not hide anything from you. With that said, no one would use debug mode in production so there really shouldn't be any fear of exposing sensitive data there. Unless you are explicitly logging this data or showing it to the user somewhere Laravel wouldn't do that in production mode.
Upvotes: 1