Are compromised private keys that much of a problem in the real world to merit such a pain in the ass, heavy handed “solution”? On paper, sure, it makes sense. In practice, you’re forcing people to complicate the process by introducing, until now, unnecessary automation and introducing the possibility of brand new points of vulnerability.

I say this as someone who does maintain legacy systems (e.g. systems), so take it with a very angry, frazzled grain of salt. But I’ve done this for years decades and many, many systems and to my knowledge, I’ve never had a compromised private key.

This just seems like people who constantly lose their house keys mandating that everyone else change their locks as often as they do.

Just their access points. They’re all flashed to OpenWRT so can’t speak for their software/firmware, but the hardware is solid.

Disclaimer: I’ve pretty much stopped printing photos at home and just take them to Walmart/Walgreens/etc so I’m a bit out of my depth here.

I’m also asking myself, is this more of a KDE Plasma printing issue or an application printing issue?

Possibly a driver issue. Are you using a CUPS driver or does Canon provide a Linux driver for the printer? In order to get the duplexer to work on my laser printer, I had to install Brother’s official Linux driver. Maybe ‘borderless’ is a feature specific to the official driver?

You might try installing the Canon software in WINE and seeing:

1. If you can print from that (not sure if it can or not)
2. If you can’t print directly from that, can the result be exported/saved to a format you can print from Linux? If so, does that addres the border issue?

Beyond that, I’m at a bit of a loss as I haven’t done home photo printing in ages. When I did, I just dealt with the borders with a paper cutter.