Indeed Pete’s explanation was quite extensive and complete.
I would just add, since you are going to have (eventually need) an external
domain that’s going to host all this i.e. example.com, I don’t see why you
simply would no build the infrastructure around it. Imagine a tree with the
trunk ex
> On Jan 26, 2016, at 10:33 AM, Ian Malone wrote:
>
> On 26 January 2016 at 17:23, Shawn Bakhtiar wrote:
>>
>>> On Jan 26, 2016, at 9:13 AM, Ian Malone wrote:
>>>
>>> On 26 January 2016 at 17:07, Shawn Bakhtiar wrote:
>>>> I couldn
> On Jan 26, 2016, at 9:10 AM, Ian Malone wrote:
>
> On 26 January 2016 at 16:57, bruce wrote:
>> What the Heck???
>>
>> So.. people who think/decide to just disable seLinux, instead of
>> diving in to "learn" it are just lazy Lord.. shaking my head..
>>
>> How about.. some might be lazy
> On Jan 26, 2016, at 9:13 AM, Ian Malone wrote:
>
> On 26 January 2016 at 17:07, Shawn Bakhtiar wrote:
>> I couldn't agree more bruce.
>>
>> It's the 1% who get paid too much for doing too little that have such
>> indulgent luxuries.
>&
I couldn't agree more bruce.
It's the 1% who get paid too much for doing too little that have such indulgent
luxuries.
The rest of us 99% have to work for it :P
> On Jan 26, 2016, at 8:57 AM, bruce wrote:
>
> What the Heck???
>
> So.. people who think/decide to just disable seLinux, inste
LOL!!!
I feel you bruce :)
I think a LOT of people are struggling (and frustrated, rightfully so) with
SELinux and simply place it in permissive mode. There is nothing wrong with
doing this. Don't buy into the fear mongering hype. The only think you have to
fear is fear itself.
If/when securi