Skip to content
This repository has been archived by the owner on May 22, 2021. It is now read-only.

CSRF protection #62

Closed
dannycoates opened this issue Jun 8, 2017 · 2 comments
Closed

CSRF protection #62

dannycoates opened this issue Jun 8, 2017 · 2 comments
Milestone

Comments

@dannycoates
Copy link
Contributor

No description provided.

@dannycoates
Copy link
Contributor Author

@abhinadduri
Copy link
Collaborator

We are currently using delete tokens to ensure that only the person who uploaded a file can delete it. These delete tokens are stored in local storage, and on our redis server. There are no other parts of the application where there could be a CSRF vulnerability (we don't have any type of user state, although I guess some sort of upload limit per browser would help stop stress attacks).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants