All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Loopback security...
Date: Mon, 21 Apr 2008 21:05:42 -0500	[thread overview]
Message-ID: <480D47F6.9080808@riverviewtech.net> (raw)

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.  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.  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?



Grant. . . .

             reply	other threads:[~2008-04-22  2:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22  2:05 Grant Taylor [this message]
2008-04-22 11:01 ` Loopback security 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
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=480D47F6.9080808@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 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.