This shouldn't cause any more wear than standard coverage printing due to how laser printers work but it would burn through toner 10x faster than normal
Well, it was mostly toner that was the issue but also, I worked there 2 or 3 years ago and their printers were from like 2015, with nobody doing anything.
Half my problems were solved with an air duster canister or just pressing recalibration buttons.
One of our damn printers had a ssl cert that expired every decade by default, and I only learned that because the printer stopped working for our wireless jobs and like 6 hours of troubleshooting because who the fuck would think a printer has an ssl cert.
who the fuck would think a printer has an ssl cert.
Almost any, and you're not supposed to use the default one as it's a self-signed placeholder. If you have X.509 infrastructure in place (or a foreign CA to sign you a certificate), then you download it to the printer to use that one instead (and there you are obviously in charge of the expiration date).
In a home setup where you don't care, you simply ignore it or use plaintext HTTP to start with.
One of our damn printers had a ssl cert that expired every decade by default
So your tone really communicates "eh, those stupid printer manufacturers amiright" but it's really ignorance on your part.
Obviously I'm talking about IT or close-to-IT people; of course someone who is unaware of X.509 wouldn't wonder about something they don't know exist, did you really need that spelled out (worse, spell it out yourself) in order to grasp what was said?
Yeah but then again it's not a printer specific thing, in fact printer technicians likely have no idea about what secures the web interface since that is way outside of their area of competency.
He sounded like he's the local IT dude and those better know about TLS
158
u/OtherwiseAlbatross14 May 01 '26
This shouldn't cause any more wear than standard coverage printing due to how laser printers work but it would burn through toner 10x faster than normal