Skip to content
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

Is this still up to date? #6

Open
Aditya94A opened this issue Oct 18, 2017 · 1 comment
Open

Is this still up to date? #6

Aditya94A opened this issue Oct 18, 2017 · 1 comment

Comments

@Aditya94A
Copy link

It's been almost a year since the last update, I was wondering whether any of the information is outdated or perhaps some best practices have evolved since last year?

@samsch
Copy link

samsch commented Mar 30, 2018

This isn't actually different from 2016, but usually the recommended password hashing algorithms are (in this order) scrypt, bcrypt, and then PBKDF2.

I would personally have the bit about xss specifically recommend only using escape-by-default templating engines, as well as mentioning that validated user data should be stored as is, and then escaped by the mechanism which displays it (templating engine).

The list should probably recommend using HTTPS for all pages, not just those with sensitive data. This was true in 2016, but is more important now with more features being https-only, and browsers openly displaying warnings for http sites.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants