Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Leonardo Rodrigues Magalhães" <leolistas@solutti.com.br>
To: Grant Taylor <gtaylor@riverviewtech.net>
Cc: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: Loopback security...
Date: Tue, 22 Apr 2008 08:01:04 -0300	[thread overview]
Message-ID: <480DC570.80303@solutti.com.br> (raw)
In-Reply-To: <480D47F6.9080808@riverviewtech.net>



Grant Taylor escreveu:
> It is my (mis)understanding that the Linux kernel treats the loopback 
> interface and / or the 127.0.0.1/8 subnet as (in a word) "sacred" and 
> as such secures it.  I believe I understand the mentality of this and 
> do not have a problem with it.
    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 !!!

> However after helping someone work around this problem (via rinetd) I 
> find my self asking wondering is it possible to disable this security 
> on the loopback interface.
    What was the problem solved/workarounded ???? Tell us what happened 
and maybe we'll tell you if using rinetd was a smart solution and, if 
it's not, maybe give you other better workaround tips.

> Is there a /proc and / or sys control entry that can be throbbed to 
> allow traffic in to and / or out of the loopback interface?
>

    No seek and hide games .... tell us what's really your problem please.

    Do you mean loopback interface to throw/receive traffic on your 
phisical network, ie, ethernet cables ??? If this is your idea, it goes 
against the whole loopback idea and i think it certainly cant be done.


-- 


	Atenciosamente / Sincerily,
	Leonardo Rodrigues
	Solutti Tecnologia
	http://www.solutti.com.br

	Minha armadilha de SPAM, NÃO mandem email
	gertrudes@solutti.com.br
	My SPAMTRAP, do not email it





  reply	other threads:[~2008-04-22 11:01 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 [this message]
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
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=480DC570.80303@solutti.com.br \
    --to=leolistas@solutti.com.br \
    --cc=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