37 ms·
This feels like the sum of many independently defensible decisions that somebody ought to have stood back from and gone "Woah, that's not OK" overall. Should w
by tialaramex 5y ago
This feels like the sum of many independently defensible decisions that somebody ought to have stood back from and gone "Woah, that's not OK" overall.
Should we do a modern rewrite of the print spooler, maybe cut it up into different chunks following modern practices and use the less risky codepaths invented since it was built? No, printing is no longer critical path for many customers, so minimal budget for this software.
Should there be a separate fancy print spooler for the people who might actually want unprivileged print requests to result in magically installing privileged device drivers? Alas this would take a rewrite, which we can't do, see above.
Should the print spooler have SYSTEM? Alas the single print spooler we ended up with because of the above decision needs SYSTEM or it will not function as intended.
Should machines with no business printing anything need Print Spoolers (which get SYSTEM)? Alas the single print spooler we ended up with also performs necessary central clean-up that must take place on systems with no print spool.
Only when you zoom out and see the result is it obvious, we should spend some of our security budget getting rid of this arrangement, it's clearly a problem waiting to happen.