New answers tagged cups
For some reason you've ended up with i386 cups-daemon installed, instead of amd64. That's why it ends up needing i386 PAM modules... To fix this, you need to remove cups-daemon and re-install the amd64 version; as root: apt-get remove cups-daemon:i386 apt-get install cups-daemon:amd64 If your dpkg architectures are set up correctly you should be able to ...
After a whole day of trial-and-error, googling, installing and deinstalling endless packages, I found which one was the bad guy: apt-get install libpam-modules:i386 was the solution. So it seems that the cups package in Debian Jessie does not officially depend on libpam-modules:i386 even though it needs it.
cups-browsed has been packaged for debian and is intended to use mdns to add equivalent functionality.
Recent versions of ghostscript include a pcl interpreter, and can work with the full range of ghostscript output formats including pdf, ps, image formats like Tiff and Jpeg, and all their known printers. You may need to compile from source. I have no Idea if this will work directly with your printer or if additional intermediate steps would be needed. As a ...
There are two general approaches to do what you want to do. printer specific method: Using the printer manufacturer provided tools and documentation configure the printer. This has the advantage of the fewest components. On the other hand you would need to trust the manufacturer of the printer to securely implement the print server with all the needed ...
I found the following article on the web just today: https://luxsci.com/blog/ssl-versus-tls-whats-the-difference.html Here is an excerpt from that document: "It used to be believed that TLS v1.0 was marginally more secure than SSL v3.0, its predecessor. However, SSL v3.0 is getting very old and recent developments, such as the POODLE vulnerability have ...
Top 50 recent answers are included