← Back to context Comment by Wirbelwind 19 hours ago Good catch, this has now been nerfed and this approach has gotten its own title 11 comments Wirbelwind Reply smaudet 16 hours ago Actually, the only secure default is to deny everything...how do you know that innocent command is actually innocent? ssl-3 16 hours ago A strange game. The only winning move is not to play. SOLAR_FIELDS 14 hours ago It’s the security mantra: the safest code is the one you never release. Code that never runs is the most secure code 6 replies → KajMagnus 19 hours ago Top 18%! I denied everything, unless I could see at a glance that it was safe (like Git diff) xg15 18 hours ago Glad I could help. I love the new title :D
smaudet 16 hours ago Actually, the only secure default is to deny everything...how do you know that innocent command is actually innocent? ssl-3 16 hours ago A strange game. The only winning move is not to play. SOLAR_FIELDS 14 hours ago It’s the security mantra: the safest code is the one you never release. Code that never runs is the most secure code 6 replies →
ssl-3 16 hours ago A strange game. The only winning move is not to play. SOLAR_FIELDS 14 hours ago It’s the security mantra: the safest code is the one you never release. Code that never runs is the most secure code 6 replies →
SOLAR_FIELDS 14 hours ago It’s the security mantra: the safest code is the one you never release. Code that never runs is the most secure code 6 replies →
KajMagnus 19 hours ago Top 18%! I denied everything, unless I could see at a glance that it was safe (like Git diff)
Actually, the only secure default is to deny everything...how do you know that innocent command is actually innocent?
A strange game. The only winning move is not to play.
It’s the security mantra: the safest code is the one you never release. Code that never runs is the most secure code
6 replies →
Top 18%! I denied everything, unless I could see at a glance that it was safe (like Git diff)
Glad I could help. I love the new title :D