9 ms·
The everlasting cycle of security fuckwittery (with some apologies to Randall Munroe's "sandboxing cycle"). 1) There is a protocol for communication that encod
by yodelshady 3y ago
The everlasting cycle of security fuckwittery (with some apologies to Randall Munroe's "sandboxing cycle").
1) There is a protocol for communication that encodes some useful heuristic for regular operations - IP addresses, for example, or ports.
2) Idiots decide that ONLY EVER COMPLETELY SAFE traffic should be allowed. As a result, all communications are gone.
3) That's not workable, so some channels have to be opened.
4) Someone develops a way to encode all the previous uses, including the necessary administrative ones, AND necessarily the malicious ones, over this protocol.
1) as 1) but with an extra layer that now does nothing.
A very* similar process exists for scripting languages. "Why are our employees so unproductive, manually doing easily automated things that security won't let them automate? -> Hey, wouldn't it be great if we could automate all the things with [X]? -> Oh noes, malware!".