From: Patrick McHardy <kaber@trash.net>
To: Cody Tubbs <tubbs@wispdirect.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ipv4options still broken (posted prev w/ no reply)...
Date: Tue, 30 May 2006 21:22:50 +0200 [thread overview]
Message-ID: <447C9B8A.20304@trash.net> (raw)
In-Reply-To: <1149011224.28886.14.camel@mbox>
Cody Tubbs wrote:
> While we're on the nth match topic and speaking of broken modules in
> pom, I posted a couple of weeks ago about the lsrr and ssrr options
> being broken in the ipv4options module. I had dialog with Fabrice, but
> it seems he doesn't have time to maintain the module anymore, or at
> least fix this issue. It's giving everyone who is using it a false
> sense of security, being that it loads, but doesn't do anything when an
> lsrr/ssrr ip option is set and passes through the module. Can this be
> removed until it's fixed? lsrr and ssrr are critical ip options to
> monitor attempting to enter your network, and people using this module
> thinking/expecting it to work can possibly get compromised via its lack
> of mojo. Thanks.
I somehow doubt that this is really a threat, but feel free to send
a patch to disable those two options until fixed.
next prev parent reply other threads:[~2006-05-30 19:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 17:47 ipv4options still broken (posted prev w/ no reply) Cody Tubbs
2006-05-30 19:22 ` Patrick McHardy [this message]
2006-05-30 21:16 ` Cody Tubbs
2006-05-30 23:05 ` Patrick McHardy
[not found] <1149033568.27117@www.broadwayinternet.com>
2006-05-30 23:46 ` Patrick McHardy
2006-05-31 4:54 ` Patrick Schaaf
2006-05-31 13:55 ` Patrick McHardy
2006-05-31 17:45 ` Cody Tubbs
2006-05-31 18:39 ` Patrick McHardy
2006-05-31 19:02 ` Cody Tubbs
2006-06-01 3:25 ` Patrick McHardy
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=447C9B8A.20304@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=tubbs@wispdirect.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.