From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: iptables rules for cups printer discovery
Date: Fri, 15 Aug 2008 10:21:12 -0500 [thread overview]
Message-ID: <48A59EE8.8090709@riverviewtech.net> (raw)
In-Reply-To: <19140-74447@sneakemail.com>
On 08/15/08 09:17, Stephen Isard wrote:
> Ok! Now I find the printers. (I also had to stick -j ACCEPT at the
> ends of the lines. You were probably taking that for granted.)
Good!
> Assuming you really mean that last "not", then my description
> seems to apply. So if a bad guy knew how take advantage of udp
> broadcasts to arbitrary high numbered ports, he could sit there waiting
> for a cups broadcast and then send his evil packets from his port 161 to
> whichever of my ports he wanted. Fortunately, such broadcasts will not
> be very frequent, since once the printers are discovered, there is no
> need to rediscover them until something changes. But still it would be
> better to match the broadcast port number. A new feature?
If you are worried about someone else spoofing an IP in your recent
list, look in to the --rttl option to have the recent list remember the
TTL values of packets and require them to be the same. This way if some
jerk off who is more hops away from you is trying to pretend to be you,
his traffic will appear to be at a different TTL than yours. This is
not fool proof, but it will sure help reduce the risk of exposure that
you are referring to.
Grant. . . .
next prev parent reply other threads:[~2008-08-15 15:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 18:51 iptables rules for cups printer discovery Stephen Isard
2008-08-14 20:00 ` Jan Engelhardt
2008-08-14 20:23 ` Stephen Isard
2008-08-14 20:37 ` Jan Engelhardt
[not found] ` <11653-43715@sneakemail.com>
[not found] ` <alpine.LNX.1.10.0808141744490.18538@fbirervta.pbzchgretzou.qr>
2008-08-14 23:01 ` Stephen Isard
2008-08-15 1:35 ` Grant Taylor
2008-08-15 1:53 ` Jan Engelhardt
2008-08-15 2:00 ` Grant Taylor
2008-08-15 2:04 ` Jan Engelhardt
2008-08-15 2:14 ` Grant Taylor
2008-08-15 2:26 ` Jan Engelhardt
2008-08-15 13:10 ` Stephen Isard
2008-08-15 13:23 ` Jan Engelhardt
2008-08-15 14:17 ` Stephen Isard
2008-08-15 15:21 ` Grant Taylor [this message]
2008-08-15 15:38 ` Stephen Isard
2008-08-15 16:16 ` Grant Taylor
2008-08-15 16:28 ` Stephen Isard
2008-08-15 18:01 ` Grant Taylor
2008-08-15 15:16 ` Grant Taylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48A59EE8.8090709@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox