55
Printing Rant! Why is this so hard?
(lemmy.one)
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
I just did a test with my Brother printer on Windows. I saw one port opened for the print protocol and four or five for various name service protocols (because I have a homelab and have screwed around with DNS a little too much, apparently). If you're opening half of all possible TCP and UDP ports to get the printing protocol to work, you're doing something wrong.
I said "for all print protocols", as in all the ones network printers have to support to get all possible clients to work.
But why would you need to get all possible clients to work? Just get the ones that are actually on your network working. And don't open your Internet-facing firewall unless for some bizarre reason you have to print from over the Internet (can't really see a critical use case for this except for outliers).
Unless you're running a web cafe or something and have to support random laptops that people bring in. At that point security is out the window anyway because who knows what will be going on your network.
The point was that the protocols are badly designed and I was talking about firewalls between subnets.
If you have to print from a location away from your network ( like on a business trip ) us tailscale!