Re: Loopback security...

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tuesday 2008-04-22 16:08, Grant Taylor wrote:
> On 04/22/08 06:01, Leonardo Rodrigues Magalhães wrote:
>
>> Are you sure you understand it right ??? What do you mean by
>> 'linux consider it secure' ?? do you mean it has no access control
>> by default ???? This happens with ALL linux network (logical and
>> phisical) ones. If you need access control on network level, then
>> you got iptables !!!
>
> No, you mis-understood me.  What I meant by "Linux considers it
> secure" is that (by default) it will not let any traffic in to our
> out of the loopback interface from / to a different interface. 
> I.e. (presuming that a bind an additional subnet (192.0.2/24 ""Test
> network) to the loopback interface and set up another station to
> route to it via the static ip on the ethernet interface.
>
> +---+                  +---+
> | A +-- - - -  - - - --+ B |
> +---+ .1 (10.0.0) .254 +---+

There is no problem with doing

	ip a f dev lo
	ip a a 127.0.0.1/8 dev eth0

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.
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Netfilter Development]     [Linux Kernel Networking Development]     [Netem]     [Berkeley Packet Filter]     [Linux Kernel Development]     [Advanced Routing & Traffice Control]     [Bugtraq]

  Powered by Linux