Implement CSRF Countermeasures #71
Labels
No labels
Bug
Cleanup/Refactor
Core Feature
Documentation
Feature
Performance Improvement
Security Improvement
UX/Accessibility
Unreproducable Bug
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: rainbownapkin/canopy#71
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We should implement CSRF countermeasures to keep sensitive actions safe.
The NPM package csrf-sync looks like it might be a good option.
We should protect all API calls that effect session state or DB, as well as channel connections.
added #35 as parent issue
changed the description
CSRF tokens now embedded in full-paged EJS templates:
83f76af6e8changed the description
CSRF tokens added to all API calls, /api/account calls updated:
106b0fcddbAdded CSRF token headers to ajax calls for /api/channel routes:
6dd8983a48Added CSRF token headers to ajax calls for /api/admin routes:
6c379321f7Added CSRF token check to socket.io connection authorization function:
4a865e8aa8CSRF countermeasure implementation complete.