From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Loopback security...
Date: Tue, 22 Apr 2008 15:16:04 -0500 [thread overview]
Message-ID: <480E4784.3060905@riverviewtech.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0804222145350.13697@fbirervta.pbzchgretzou.qr>
On 04/22/08 14:48, Jan Engelhardt wrote:
> There is no problem with doing
>
> ip a f dev lo
> ip a a 127.0.0.1/8 dev eth0
Ok.
> However, ping 127.0.0.2 will fail of course, yes it is a special
> handling inside linux (but not really on the topic of "secure"),
> code-wise it is just like 240.0.0.0/8 which was not routed a few
> weeks ago until a patch changed it.
I had not considered any thing other than 127.0.0.1 as I don't use the
other millions of addresses in the loopback network.
Are you saying that what I'm calling a ""security feature is really a
misconception and a side effect of other parts of the kernel?
Further, can you give some back history on the 240/8 network or point me
in a direction to do some reading?
Grant. . . .
next prev parent reply other threads:[~2008-04-22 20:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 2:05 Loopback security Grant Taylor
2008-04-22 11:01 ` Leonardo Rodrigues Magalhães
2008-04-22 14:08 ` Grant Taylor
2008-04-22 16:04 ` Pascal Hambourg
2008-04-22 19:43 ` Grant Taylor
2008-04-23 10:51 ` Pascal Hambourg
2008-04-25 20:00 ` Grant Taylor
2008-04-22 20:51 ` Petr Pisar
2008-04-23 9:31 ` Pascal Hambourg
2008-04-23 9:45 ` Leonardo Rodrigues Magalhães
2008-04-22 16:50 ` Leonardo Rodrigues Magalhães
2008-04-22 20:07 ` Grant Taylor
2008-04-22 20:25 ` Leonardo Rodrigues Magalhães
2008-04-23 0:38 ` Grant Taylor
2008-04-23 9:07 ` Pascal Hambourg
2008-04-23 9:44 ` Pascal Hambourg
2008-04-22 19:48 ` Jan Engelhardt
2008-04-22 20:16 ` Grant Taylor [this message]
2008-04-23 15:22 ` Jan Engelhardt
2008-04-25 20:11 ` 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=480E4784.3060905@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