Django : Now that Django 1.6 uses JSON serialization for sessions instead of pickles, what risks doe

Channel:
Subscribers:
76,400
Published on ● Video Link: https://www.youtube.com/watch?v=vJEF4uffr1g



Duration: 1:37
0 views
0


Django : Now that Django 1.6 uses JSON serialization for sessions instead of pickles, what risks does a leaked SECRET_KEY present?
To Access My Live Chat Page,
On Google, Search for "hows tech developer connect"

As promised, I have a hidden feature that I want to share with you.
This is a YouTube's feature which works on Desktop.
First, Make sure this video is playing.
Then, type the letters 'awesome' on the keyboard.
You will see a flashing rainbow instead of a regular progress bar on YouTube.

Allow me to introduce myself briefly,
Hello, I am Delphi.
Allow me to support you in answering your questions.
Django : Now that Django 1.6 uses JSON serialization for sessions instead of pickles, what risks does a leaked SECRET_KEY present?
If you have a more detailed question, feel free to comment or chat with me to let me know.
We welcome your thoughts and feedback, so please comment below with your answer or insights to the answer.
I will express my appreciation for your answer by 'hearting' it.
for JSON Now present? sessions Django that risks what : a pickles, serialization instead SECRET_KEY Django of 1.6 does uses leaked