Its interesting tangent that the "confused deputy" security problem was first identified in a compiler, back in the days when people paid to have their code com

Its interesting tangent that the "confused deputy" security problem was first identified in a compiler, back in the days when people paid to have their code compiled. This led towards "capabilities" and lots of operating system design that is now in vogue again. https://en.wikipedia.org/wiki/Confused_deputy_problem https://en.wikipedia.org/wiki/Confused_deputy_problem (this #include problem can be thought of as a confused deputy vulnerability. The compiler shouldn't have the capability to read the password file, and if it did, it is a confused deputy to be wielding that cap on behalf of its user, instead of wielding the caps it gets from the user). Its sad that the links to Norm Hardy's original write-up all seem broken. https://web.archive.org/web/20031205034929/http://www.cis.upenn.edu/~KeyKOS/ConfusedDeputy.html https://web.archive.org/web/20031205034929/http://www.cis.up... Norm was a brilliant mind. He was talking and thinking about capabilities right up until the end.