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.

Sign up for GitHub

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

Jump to bottom

Add security design note #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add security design note #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/SECURITY_DESIGN.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
The core idea around the security design is to build for multiple authorization
levels. The core reason, surprisingly, is for easy caching. One of the ways that
many existing forums have some users invalidate a lot of caches is that they
serve up special content for moderators at the same URLs that normal users use.
This means more cache misses, intrinsically.

To avoid this, and to improve security, functionality should be locked at
multiple security levels, so that normal moderator browsing can have some
additional features, but generally ones that can be added through loading some
additional resources, not modifying the existing page.