I got this bug from a Debian user. I'm not sure how insecure having
things the way they are is, but being able to specify what interfaces to
listen on is pretty standard on most daemons and kinda neat.
----- Forwarded message from Manel Marin -----
lprng listens on all interfaces
This is a safety risk!
I have not seen the way of restrict interfaces to e.g.: 127.0.0.1 and 10.0.0.1
as it can be done with other major daemons (named, apache, postfix, samba)
with options like "listen on", "bind", or "interface"
When using lprng at home without firewall (most common setup with newbies)
lprng is active in internet interface waiting the next exploit to appear :-(
----- End forwarded message -----
--
Craig Small VK2XLZ GnuPG:1C1B D893 1418 2AF4 45EE 95CB C76C E5AC 12CA DFA5
Eye-Net Consulting http://www.eye-net.com.au/ <[EMAIL PROTECTED]>
MIEEE <[EMAIL PROTECTED]> Debian developer <[EMAIL PROTECTED]>
-----------------------------------------------------------------------------
If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body. For the impatient,
to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED]
with: | example:
subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED]
If you have major problems, send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------
