Implement better CSRF token #4
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-thirtybees/sendtoafriend#4
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?
Current token is constant, same for all visitors, and valid forever.
We should implement new mechanism that would generate unique token for every visitor. Token could be used only once, and then replaced with a new one.
This will not fix the spam issue, but it could help with 'dumb' bots.