All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: "Justin Mattock" <justinmattock@gmail.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: NetLabel
Date: Wed, 4 Jun 2008 10:31:33 -0400	[thread overview]
Message-ID: <200806041031.33060.paul.moore@hp.com> (raw)
In-Reply-To: <dd18b0c30806032355v44c0b5d2u965e3e7a65ba2e24@mail.gmail.com>

On Wednesday 04 June 2008 2:55:15 am Justin Mattock wrote:
> Hello; Hopefully this is the right list to post this question,
> after looking at  NetLabel, in dmesg I couldn't help but see:
> [    0.570655] NetLabel: Initializing
> [    0.570660] NetLabel:  domain hash size = 128
> [    0.570663] NetLabel:  protocols = UNLABELED CIPSOv4
> [    0.570730] NetLabel:  unlabeled traffic allowed by default
>
> "unlabeled traffic allowed by default."
> is this similar to selinux (handle_unkown=deny, if so is there an
> option to change this to "unlabeled traffic deny."

Nope, the two are completely unrelated.  By default, NetLabel allows 
unlabeled traffic to pass (meaning the netlbl_skbuff_getattr() function 
returns an empty secattr and no error, the LSM does the actual packet 
pass/drop) so as to keep networking working for the majority of users 
who do not configure NetLabel.  If you were to disable unlabeled 
traffic using NetLabel only CIPSO and static/fallback (using 2.6.25 or 
greater) labeled traffic would be allowed into the system.

Unless you really know what you are doing I wouldn't mess with this 
setting.

> Also is there a location for this in the kernel i.g. /proc/sys/net/*
> regards;

There are some sysctl variables which offer control of the 
NetLabel/CIPSO functionality they do no toggle the unlabeled allow/deny 
behavior, for that you need the netlabel_tools package, specifically 
netlabelctl.

 * http://netlabel.sf.net

-- 
paul moore
linux @ hp

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2008-06-04 14:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04  6:55 NetLabel Justin Mattock
2008-06-04 14:31 ` Paul Moore [this message]
2008-06-04 19:05   ` NetLabel Justin Mattock
2008-06-04 19:14     ` NetLabel Paul Moore
2008-06-04 19:25       ` NetLabel Justin Mattock
  -- strict thread matches above, loose matches on Subject: below --
2012-04-26 16:12 Netlabel Christophe Hauser

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=200806041031.33060.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=justinmattock@gmail.com \
    --cc=selinux@tycho.nsa.gov \
    /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.