Randy McMurchy wrote:
This reminds me of something I've been meaning to bring up for a long
time. In the Samba instructions we recommend using Stunnel to encrypt
the use of SWAT, as it requires the root password and it is sent clear
text over the wire if not Stunneled.
Should we also recommend, and provide instructions for, encrypting the
use of the CUPS web interface as well? To me, it is the exact same
thing (requires root password sent over the wire as clear text, if not
encrypted)
Why not use encryption support from CUPS itself instead? Also, for
printing over https, this symlink is needed: ln -s ipp
/usr/lib/cups/backend/https
One more side note: I think it is a good idea to make CUPS listen only
on 127.0.0.1:631 and dsable browsing if remote management and printer
sharing are not needed.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
