From: "Stephen Isard" <y8ju2p902@sneakemail.com>
To: netfilter@vger.kernel.org
Subject: Re: iptables rules for cups printer discovery
Date: Fri, 15 Aug 2008 12:28:41 -0400 (EDT) [thread overview]
Message-ID: <21281-33344@sneakemail.com> (raw)
In-Reply-To: <48A5ABE7.2040008@riverviewtech.net>
> Um, if they have gotten a system in to your LAN I think you have bigger
> problems. If this is a real concern, I'd suggest that you look in to 802.1x
> (port) authentication.
This is a large university department where students and visitors use
the lan. The computing officers are highly competent and doing their
best to provide security, but, as you know, it's a constant battle.
> Also remember that you can adjust the length of time for the "recent" window.
Right.
> You can probably also mitigate the window by looking for the closing
> connection (at least with TCP)
This particular case involves udp.
Thanks for your advice.
next prev parent reply other threads:[~2008-08-15 16:28 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
2008-08-15 15:38 ` Stephen Isard
2008-08-15 16:16 ` Grant Taylor
2008-08-15 16:28 ` Stephen Isard [this message]
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=21281-33344@sneakemail.com \
--to=y8ju2p902@sneakemail.com \
--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