From: Patrick McHardy <kaber@trash.net>
To: "David S. Miller" <davem@davemloft.net>
Cc: laforge@netfilter.org, netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 1/2] New ipt_TTL target
Date: Sat, 27 Aug 2005 05:31:00 +0200 [thread overview]
Message-ID: <430FDE74.7030800@trash.net> (raw)
In-Reply-To: <20050826.123018.21840974.davem@davemloft.net>
David S. Miller wrote:
> From: Harald Welte <laforge@netfilter.org>
> Date: Fri, 26 Aug 2005 20:31:51 +0200
>
>
>>+config IP_NF_TARGET_TTL_INC
>>+ bool 'TTL incrementing support (DANGEROUS)'
>>+ depends on IP_NF_TARGET_TTL
>>+ help
>>+ This option enables functionality to increment and set the TTL
>>+ value of the IP header to arbitrary values. This is EXTREMELY
>>+ DANGEROUS since you can easily create immortal packets that loop
>>+ forever on the network. Please only enable if you really know
>>+ that you will need it.
>>+
>
>
> I think it's best to kill this option. Just put the "this is
> DANGEROUS" comment into the help text for IP_NF_TARGET_TTL, ok?
>
> Similarly for the ipv6 hoplimit target too.
If we want to make sure, we simply print a message in the iptables
userspace command when someone uses this option. If this is too
extreme, a comment in the man-page will probably help to reach more
people than in the kernel-help text.
next prev parent reply other threads:[~2005-08-27 3:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 18:31 [PATCH 1/2] New ipt_TTL target Harald Welte
2005-08-26 19:30 ` David S. Miller
2005-08-27 3:31 ` Patrick McHardy [this message]
2005-08-27 3:53 ` David S. Miller
2005-08-27 11:07 ` Harald Welte
2005-08-27 13:21 ` Harald Welte
2005-08-27 13:22 ` [PATCH 2/2] New ip6t_HL target Harald Welte
2005-08-28 5:38 ` David S. Miller
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=430FDE74.7030800@trash.net \
--to=kaber@trash.net \
--cc=davem@davemloft.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.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 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.