public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: PolarStorm <developer@clinicsearch.com>
To: cygwin@cygwin.com
Subject: Re: Are there any SELinux tools available for Cygwin?
Date: Tue, 03 Jun 2014 08:58:00 -0000	[thread overview]
Message-ID: <1401785919671-109064.post@n5.nabble.com> (raw)
In-Reply-To: <538CBD76.4030903@etr-usa.com>

Warren Young wrote
> On 5/31/2014 12:33, PolarStorm wrote:
>> I'd like to
>> refrain from having to run long remote sessions on each machine while
>> experimentally editing all the various policy files. Downloading all
>> files
>> in
>> one go and doing analysis and editing locally, is why I wanted to do this
>> on Cygwin.
> 
> How is that easier?  You have to test each experimental edit, and that 
> requires a Linux kernel running SELinux.  Cygwin is not a Linux kernel.
> 
> Personally, if I were still experimenting, I'd spin up a VM configured 
> like the system I intended to modify, do my work on it, then ship a 
> completed policy set to the remote system.  Linux VM how-tos are 
> off-topic here, though.

Yes, I'm used to VM's. This is probably the way I'll end up doing it.  
It's to laborious for me to try to compile all these tools on Cygwin.
In addition, I wouldn't know what would be compatible with what. 


>> Another
>> point is that there seem to exist ~3 different "flavors" of SELinux
>> implementations,
> 
> What point are you making here, exactly?  Do you want Cygwin to emulate 
> one of them, or all of them, or none of them?
> I think all three choices are doomed, each for a different reason.

In an ideal world, I would have asked to be able to deal with all of them,
but at this point "any one" could also be helpful.

But it would be more interesting to hear why you think all of them are
"doomed"? 

Thanks for taking the time to give a proper answer, I very much appreciate
it. 

Best Wishes,



--
View this message in context: http://cygwin.1069669.n5.nabble.com/Are-there-any-SELinux-tools-available-for-Cygwin-tp108952p109064.html
Sent from the Cygwin list mailing list archive at Nabble.com.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2014-06-03  8:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-30 16:04 PolarStorm
2014-05-30 19:57 ` Warren Young
2014-05-31 12:37   ` PolarStorm
2014-05-31 13:32     ` Robert Pendell
2014-05-31 18:55       ` PolarStorm
2014-06-02 18:08         ` Warren Young
2014-06-03  8:58           ` PolarStorm [this message]
2014-06-03 10:35             ` Andrey Repin
2014-06-03 19:20             ` Warren Young
2014-06-03 20:00               ` Christopher Faylor

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=1401785919671-109064.post@n5.nabble.com \
    --to=developer@clinicsearch.com \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).