Displaying 4 results from an estimated 4 matches for "basicis".
Did you mean:
basic_s
2017 Apr 12
3
bind vs. bind-chroot
Hi,
On my public servers, I usually run BIND for DNS. I see CentOS offers a
preconfigured (sort of) bind-chroot package. I wonder what's the
effective benefit of this vs. a "normal" BIND setup without chroot. On
my Slackware servers, I have a rather Keep-It-Simple approach to all
things security, e. g. run no unneed services, open only needed ports
etc. but I don't run the extra
2017 Apr 12
0
bind vs. bind-chroot
On 4/12/2017 3:11 PM, Nicolas Kovacs wrote:
> On my public servers, I usually run BIND for DNS. I see CentOS offers a
> preconfigured (sort of) bind-chroot package. I wonder what's the
> effective benefit of this vs. a "normal" BIND setup without chroot. On
> my Slackware servers, I have a rather Keep-It-Simple approach to all
> things security, e. g. run no unneed
1998 Jul 15
0
Re: RedHat 5.X Security Book
...wat you are using the book for..I myself have been
trying for a long time to find a document that describes basic RedHat and
Linux security, what to look for, inherent dangers etc etc.
So I was overjoyed when I found this book. No, I am not depending on it as
a sole source of information, but the basicis that it covers simply do not
get repeatadly posted to the lists you mentioned, at least not that I have
seen. I think it is a wonderful intro into system security, but it should
be made clear that it is not intended as a "fix-all".
Just my two cents.
-- Jason Welman
-----Original Mess...
2017 Apr 13
4
bind vs. bind-chroot
On 04/12/2017 06:18 PM, John R Pierce wrote:
> On 4/12/2017 3:11 PM, Nicolas Kovacs wrote:
>> On my public servers, I usually run BIND for DNS. I see CentOS offers a
>> preconfigured (sort of) bind-chroot package. I wonder what's the
>> effective benefit of this vs. a "normal" BIND setup without chroot. On
>> my Slackware servers, I have a rather