Closed Luca0208 closed 8 years ago
The only useful 'security standard' for ComputerCraft is: "Don't store sensitive data in ComputerCraft."
Anything else is better covered elsewhere. Just like one shouldn't roll their own crypto, making security recommendations is best left to the professionals.
On Feb 9, 2016, at 11:53, Luca S notifications@github.com wrote:
This might be good to prevent insecure programs.
You can view, comment on, or merge this pull request online at:
https://github.com/oeed/CraftOS-Standards/pull/51
Commit Summary
Added Security Standards File Changes
A Security-Standards/README.md (7) Patch Links:
https://github.com/oeed/CraftOS-Standards/pull/51.patch https://github.com/oeed/CraftOS-Standards/pull/51.diff — Reply to this email directly or view it on GitHub.
Well, if you have something like a password lock, using sha256 might be a reasonable standard.
While this category is a good idea, there is no need to create one when there are no standards for it. Besides, your README is short and unusable (why should contributors think that your proposal is safe? Go ahead and make an insecure standard, it will fit into the category anyway (good luck getting it recommended
though)). Rejected.
@Luca0208 also, "Using SHA256" is not a standard.
This might be good to prevent insecure programs.