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

Toxcore needs a red team #211

Closed
GrayHatter opened this issue Oct 25, 2016 · 9 comments
Closed

Toxcore needs a red team #211

GrayHatter opened this issue Oct 25, 2016 · 9 comments
Labels
P3 Low priority suggestion Suggestions
Milestone

Comments

@GrayHatter
Copy link

No description provided.

@GrayHatter GrayHatter added the suggestion Suggestions label Oct 25, 2016
@GrayHatter GrayHatter added this to the meta milestone Oct 25, 2016
@sudden6
Copy link

sudden6 commented Oct 26, 2016

What's a red team and what does it do?

@dvor
Copy link
Member

dvor commented Oct 26, 2016

A red team is an independent group that challenges an organization to improve its effectiveness.

When used in a hacking context, a red team is a group of white-hat hackers that attack an organization's digital infrastructure as an attacker would in order to test the organization's defenses

https://en.wikipedia.org/wiki/Red_team

@isotoxin
Copy link

Ha! You guys just do nothing and this is main problem. Red team...

@Diadlo
Copy link

Diadlo commented Oct 26, 2016

@isotoxin Are you sure?
https://github.com/TokTok/c-toxcore/pulse/monthly

Toktok has a plan and go step by step to the goal

@Renha
Copy link

Renha commented Oct 26, 2016

ha, look, it's mr. @isotoxin aka 'Updated 21 days ago' by himself

@isotoxin
Copy link

No one bug was fixed last year.
No one optimization was done last year.
No one new feature was implemented last year.

Toxcore! Most stable code ever!

@Diadlo
Copy link

Diadlo commented Oct 26, 2016

@isotoxin If you read toktok plan on toxcore (sorry for previous broken link. Updated now) there is no bugfixes. But, as it appears, you related with coding => you should understand, that tests, documentation, code cleanup and refactoring make notorious bugfixes easier in the future.

@TokTok TokTok locked and limited conversation to collaborators Oct 26, 2016
@GrayHatter
Copy link
Author

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.

@iphydf iphydf modified the milestone: meta Jan 10, 2017
@TokTok TokTok unlocked this conversation Jan 12, 2017
@iphydf iphydf added the P3 Low priority label Jan 12, 2017
@iphydf iphydf added this to the v0.2.x milestone Jul 16, 2018
@iphydf
Copy link
Member

iphydf commented Feb 4, 2022

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.

@iphydf iphydf closed this as completed Feb 4, 2022
@iphydf iphydf modified the milestones: v0.2.x, meta Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Low priority suggestion Suggestions
Projects
None yet
Development

No branches or pull requests

7 participants