-
Notifications
You must be signed in to change notification settings - Fork 303
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
Generate a new SECRET_KEY during first time setup #4213
Comments
aronasorman
added a commit
to aronasorman/ka-lite
that referenced
this issue
Sep 24, 2015
aronasorman
added a commit
to aronasorman/ka-lite
that referenced
this issue
Sep 25, 2015
aronasorman
added a commit
to aronasorman/ka-lite
that referenced
this issue
Sep 25, 2015
aronasorman
added a commit
to aronasorman/ka-lite
that referenced
this issue
Sep 25, 2015
aronasorman
added a commit
to aronasorman/ka-lite
that referenced
this issue
Sep 25, 2015
aronasorman
added a commit
to aronasorman/ka-lite
that referenced
this issue
Sep 25, 2015
aronasorman
added a commit
to aronasorman/ka-lite
that referenced
this issue
Sep 28, 2015
Fixes learningequality#4213. Conflicts: kalite/settings/base.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Branch: all the branches
Expected behaviour: Arbitrary user doesn't know what their installation's secret key is.
Actual behaviour: Our secret key is not just shared across all installations, it's public as well! This means that any of the methods described in this stack overflow answer is vulnerable to attack.
So we should generate a key that will always be read by KA Lite, even if a different settings object is specified.
The text was updated successfully, but these errors were encountered: