4 ms·
Apart from the obvious compatibility disaster, what kind of skeletons does Microsoft have in their printing system that the choice of C library creates those co
by antiloper 10mo ago
Apart from the obvious compatibility disaster, what kind of skeletons does Microsoft have in their printing system that the choice of C library creates those compatibility issues in the first place?
- stackskipton 10mo agoPrint Spooler has had some bad security vulnerabilities. Example: https://www.cisa.gov/news-events/alerts/2021/06/30/printnightmare-critical-windows-print-spooler-vulnerability https://www.cisa.gov/news-events/alerts/2021/06/30/printnigh... I don’t know if this C library helps mitigate this but Print Spooler is not “it just works” either.
- vintagedave 10mo agoThe UCRT is just the newer, Windows-component version of the MSVCRT, the one they’re worried about. It’s even available for XP. > will intentionally fail to print to remote print servers Why would a more secure local print driver refuse to talk to _remote_ print servers? What is so untrustable about what comes over the wire, and if it is, how can they trust the print server is or is not one is claims to be and can be talked to?
- tonyedgecombe 10mo agoMy guess is it’s riddled with vulnerabilities. I used to write some print management software and found it very easy to crash the spooler just from routine API calls. Not only that but it seemed every time they fixed a vulnerability some piece of functionality broke.