Flask Academy · 课时

SECRET_KEY 与签名 Cookie

了解 Flask 如何安全地为会话数据签名

SECRET_KEY 与签名 Cookie 是 CoddyKit 上的免费 Flask Academy 课时。这是第 2 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Flask Academy 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Flask Academy 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Where Sessions Live

By default Flask stores the whole session inside a cookie in the user's browser, not on your server. That has big implications.

The Tampering Problem

If data lives in the browser, a user could edit it. Flask stops that by signing the cookie so changes are detectable.

Meet the SECRET_KEY

Signing needs a secret. The SECRET_KEY is the private value Flask uses to stamp and verify every session cookie. 🔑

app.config['SECRET_KEY'] = 'change-me'

No Key, No Sessions

Touch the session without a SECRET_KEY set and Flask raises a RuntimeError. It refuses to sign with nothing.

Signed, Not Encrypted

Important: a default session cookie is signed, not encrypted. Anyone can read it, so never store true secrets inside.

How Signing Verifies

On each request Flask recomputes the signature from the cookie and the key. A mismatch means tampering, so the session is rejected.

Make It Long and Random

A strong SECRET_KEY should be long and unpredictable. Generate one with the secrets module rather than typing a word.

import secrets
key = secrets.token_hex(32)

Never Hardcode in Git

Keep the SECRET_KEY out of source control. Load it from an environment variable so each deploy has its own value.

import os
app.config['SECRET_KEY'] = os.environ['SECRET_KEY']

Rotating the Key

Change the SECRET_KEY and every existing session signature stops matching. All users get logged out at once.

Same Key Everywhere

Run several app instances behind a load balancer? They must share one SECRET_KEY or each will reject the others' cookies.

Server-Side Alternative

Need bigger or hidden session data? Extensions like Flask-Session keep it on the server and store only an id in the cookie.

Quick Check

Think about what the default Flask session cookie actually protects.

Recap

You saw that SECRET_KEY signs session cookies to catch tampering. Make it long, load it from the environment, and never commit it. 🔐

常见问题解答

「SECRET_KEY 与签名 Cookie」课时是免费的吗？

是的 — 「SECRET_KEY 与签名 Cookie」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Flask Academy 课程的其余内容，请升级到 CoddyKit PRO。 Flask Academy 课程共包含 4 节课。

「SECRET_KEY 与签名 Cookie」这节课中我会学到什么？

了解 Flask 如何安全地为会话数据签名你通过在浏览器中直接运行的动手代码来练习 Flask Academy，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Flask Academy 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Flask Academy 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 2 节课，共 4 节。

「SECRET_KEY 与签名 Cookie」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Flask Academy 课中编写并运行代码吗？

能。每节 Flask Academy 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Flask Academy