All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel J Walsh <dwalsh@redhat.com>
To: Miroslav Grepl <mgrepl@redhat.com>, eric gisse <jowr.pi@gmail.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: Some of our customers are looking to turn on SELinux but they also want to use CSP from Symantec
Date: Tue, 06 Jan 2015 08:53:37 -0500	[thread overview]
Message-ID: <54ABE8E1.7010908@redhat.com> (raw)
In-Reply-To: <54ABAEBC.90308@redhat.com>


On 01/06/2015 04:45 AM, Miroslav Grepl wrote:
> On 12/19/2014 08:54 PM, Daniel J Walsh wrote:
>> On 12/19/2014 02:44 PM, eric gisse wrote:
>>>> Why disabling SELinux is important? Because both SELinux and CSP
>>>> are doing the same thing, except CSP does it better!
>>> I wonder how Symantec backs that claim up.
>> Well that might be the same case in certain things,
> Yes, but really only in certain things.
>>   but when it comes to
>> multi-tenant situations, with MCS Separation. CSP has no answer.
>>> On Fri, Dec 19, 2014 at 10:41 AM, Daniel J Walsh <dwalsh@redhat.com>
>>> wrote:
>>>> Currently Symantec requires SELinux be disabled, claiming there is
>>>> conflicts in the kernel modules.
>>>>
>>>> http://www.symantec.com/connect/forums/does-scsp-agent-support-selinux
>>>>
>>>> As the customer wants to take advantage of certain  SELinux features
>>>> like sVirt for VMs and Docker Containers, this conflict is coming
>>>> to a head.
>>>>
>>>> Is anyone familiar with whether or not this is a real conflict or just
>>>> something assumed by Symantec?
>>>>
>>>> The customer like Symantec's ability to do intrusion detection and
>>>> remote logging and configuration of CSB.
>>>>
>>>> Bottom line the customer wants both.
>>>> _______________________________________________
>>>> Selinux mailing list
>>>> Selinux@tycho.nsa.gov
>>>> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
>>>> To get help, send an email containing "help" to
>>>> Selinux-request@tycho.nsa.gov.
>>> _______________________________________________
>>> Selinux mailing list
>>> Selinux@tycho.nsa.gov
>>> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
>>> To get help, send an email containing "help" to
>>> Selinux-request@tycho.nsa.gov.
>>>
>>>
>> _______________________________________________
>> Selinux mailing list
>> Selinux@tycho.nsa.gov
>> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
>> To get help, send an email containing "help" to
>> Selinux-request@tycho.nsa.gov.
>
> _______________________________________________
> Selinux mailing list
> Selinux@tycho.nsa.gov
> To unsubscribe, send email to Selinux-leave@tycho.nsa.gov.
> To get help, send an email containing "help" to
> Selinux-request@tycho.nsa.gov.
>
>
BTW, we have heard back from Semantec and they plan on supporting
SELinux in a soon to be released update.

We shall see.

  reply	other threads:[~2015-01-06 13:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-19 16:41 Some of our customers are looking to turn on SELinux but they also want to use CSP from Symantec Daniel J Walsh
2014-12-19 17:59 ` Casey Schaufler
2014-12-19 22:09   ` Paul Moore
2014-12-19 19:44 ` eric gisse
2014-12-19 19:54   ` Daniel J Walsh
2015-01-06  9:45     ` Miroslav Grepl
2015-01-06 13:53       ` Daniel J Walsh [this message]
2014-12-19 20:02   ` Casey Schaufler

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=54ABE8E1.7010908@redhat.com \
    --to=dwalsh@redhat.com \
    --cc=jowr.pi@gmail.com \
    --cc=mgrepl@redhat.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.