I mean, you can use something like the lightweight containers generated by firejail, where the program just lacks write permission to the filesystem or network access, stuff like that.
Not quite. I believe they are just splitting CUPS up. The core is just going to be deal with driverless printers. Other code goes into other projects to become adaptors for old printers to appear as driverless printers that CUPS connects to.
That’s also a solution for Windows users if they can’t get some future version of Windows to work with the thing. You get a dinky Linux box, like a Raspberry Pi or something, and just set it up as a print server.
It’s hard to hear what Microsoft is saying over the sound of my 15 year-old printers running on CUPS.
lp0 on fireJust a heads up some of those old drivers are just encapsulated perl scripts with root access. Easy network target for bad actors.
Interesting. I wonder if it’d be practical to containerize them by default.
Oh my god please don’t make me have to debug docker or k8s printer drivers
I mean, you can use something like the lightweight containers generated by
firejail, where the program just lacks write permission to the filesystem or network access, stuff like that.deleted by creator
Not quite. I believe they are just splitting CUPS up. The core is just going to be deal with driverless printers. Other code goes into other projects to become adaptors for old printers to appear as driverless printers that CUPS connects to.
“The Paper!”
That’s also a solution for Windows users if they can’t get some future version of Windows to work with the thing. You get a dinky Linux box, like a Raspberry Pi or something, and just set it up as a print server.