Public
- Public
- Network
- Groups
- Featured
- Popular
- People

Venn diagram of the sux rule showing you should always use a safe language, isolate the code in a sandbox, or not process exogenous inputs. The intersection of sandbox-free, unsafe, and exogenous is labeled NO and an arrow points to it saying Doom! Don't do all three.

Download link

Venn diagram of the sux rule showing you should always use a safe language, isolate the code in a sandbox, or not process exogenous inputs. The intersection of sandbox-free, unsafe, and exogenous is labeled NO and an arrow points to it saying Doom! Don't do all three.
https://media.hachyderm.io/media_attachments/files/111/216/780/761/314/313/original/61c6c7de0fc0254d.png

Notices where this attachment appears

Embed this notice
Kelly Shortridge (shortridge@hachyderm.io)'s status on Thursday, 12-Oct-2023 06:52:42 JST Kelly Shortridge

new post: the SUX Rule for safer code https://kellyshortridge.com/blog/posts/the-sux-rule-for-safer-code/
it’s short for Sandbox-free - Unsafe - eXogenous. If your code does all three of:
- running without a sandbox
- written in an unsafe language
- processing exogenous inputs
it’s certain your code SUX.
it’s basically me tweaking Chromium’s excellent Rule of Two because it conflicts with Star Wars lore (among other reasons I describe)
#cybersecurity #memorysafety

In conversation about a year ago from hachyderm.io permalink