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.

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

Known security risks #69

Open
Jaymassena opened this issue Feb 19, 2017 · 2 comments
Open

Known security risks #69

Jaymassena opened this issue Feb 19, 2017 · 2 comments
Labels

Comments

@Jaymassena
Copy link
Member

This is used for now to track known gaps in our security.

@Jaymassena
Copy link
Member Author

Jaymassena commented Feb 21, 2017

  • Invites do not expire: We could add an expiration timestamp and require that now <= timestamp for an invite to be considered valid for group/channel membership.
  • Invites can be forwarded: They are like golden tickets that can be used by anyone who possesses it but it can only be used once.
  • We rely on firebase security throttling to protect against massive user account spamming.

@Jaymassena
Copy link
Member Author

As of 2.2

  • Branch invite links are good forever: We could add an expiration timestamp and require that now <= timestamp for an invite to be considered valid for channel membership. We could also use a branch feature that make a link good for one use only.
  • Branch invite links can be forwarded: They are like golden tickets that can be used by anyone who possesses it.
  • We rely on firebase security throttling to protect against massive user account spamming.

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

No branches or pull requests

1 participant