-
Notifications
You must be signed in to change notification settings - Fork 284
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
Toxcore needs a red team #211
Comments
What's a red team and what does it do? |
|
Ha! You guys just do nothing and this is main problem. Red team... |
@isotoxin Are you sure? Toktok has a plan and go step by step to the goal |
ha, look, it's mr. @isotoxin aka 'Updated 21 days ago' by himself |
No one bug was fixed last year. Toxcore! Most stable code ever! |
I'm going to attempt to slow this flamebate down a bit by locking to collaborators for now. This is a meta issue and in no way the main problem. (I'm not sure why you think than @isotoxin unless you're just fusterated, which I can understand; Tox has been somewhat slow in the past) I created this issue in case someone else wants to take it on while I work on tox-named, as well as upgrading net_crypto code. Once that's done I'll take another look at this myself, meanwhile I can't forget about it. The reason I opened this is because I'm planning to change how friends find each other, so we can drastically reduce data usage. While that's VERY important I also don't want to make tox less secure. Having a red team would be a step in the right direction to making AND KEEPING Tox secure. |
No red team for now. We're about 5 people more or less actively working on the code these days. Let's reconsider at some point in the future when we have more resources. |
No description provided.
The text was updated successfully, but these errors were encountered: