A security-oriented Go compiler(github.com)
github.com
A security-oriented Go compiler
https://github.com/kevin-valerio/cybergo
4 comments
cybergo is a security-focused fork of the Go toolchain. In a very simple phrasing, cybergo is a copy of the Go compiler that finds bugs.
Is the plan to contribute them back to Go?
How is a one person fork of Go in any way going to ever be more secure than the original which is developed by many people? Why should I trust your changes? Is this actually an adversarial project that will hide and rug pull down the road?
How is a one person fork of Go in any way going to ever be more secure than the original which is developed by many people? Why should I trust your changes? Is this actually an adversarial project that will hide and rug pull down the road?
1. "Is the plan to contribute them back to Go?" - No. They won't accept the up-streams. See https://github.com/golang/go/issues/30613
2. "How is a one person fork of Go in any way going to ever be more secure than the original which is developed by many people? " - Read the README.
3. "Why should I trust your changes?" - You don't have to. The same reasons you don't have to trust the Github project you're cloning.
4. "Is this actually an adversarial project that will hide and rug pull down the road?" - Read the code.
Sarcasm aside, the objective is "helping to find bugs in Go codebases via built-in security implementations". That's mainly used for fuzzing and testing. Don't deploy you compiled binary on production with that compiler.
2. "How is a one person fork of Go in any way going to ever be more secure than the original which is developed by many people? " - Read the README.
3. "Why should I trust your changes?" - You don't have to. The same reasons you don't have to trust the Github project you're cloning.
4. "Is this actually an adversarial project that will hide and rug pull down the road?" - Read the code.
Sarcasm aside, the objective is "helping to find bugs in Go codebases via built-in security implementations". That's mainly used for fuzzing and testing. Don't deploy you compiled binary on production with that compiler.
If the Go team will not accept your changes, I would trust their judgement over yours 100%