On Monday 30 November 2009 22:40:07 Hal Murray wrote:
g...@czarc.net said:
...
A written description of the security policy is a must!
...
Is the idea of a single one-size-fits-all security policy reasonable? I
think Fedora has a broad range of users.
No. Initially, I recommend
On Monday 30 November 2009 18:16:50 Adam Williamson wrote:
On Mon, 2009-11-30 at 15:17 -0500, Eric Christensen wrote:
Gene,
(Ahh... someone with a similar background...)
So the biggest question, to me, is to what standard do we start?
There are plenty to choose from from DISA to NIST.
On Tuesday 01 December 2009 13:56:51 Adam Williamson wrote:
On Tue, 2009-12-01 at 12:47 -0500, Gene Czarcinski wrote:
I suspect that most commercial and government customers will be
interested in Red Hat Enterprise Linux rather than Fedora. But, Fedora
is the technology base on which
On Tuesday 01 December 2009 13:04:02 Eric Christensen wrote:
On Tue, Dec 1, 2009 at 12:47, Gene Czarcinski g...@czarc.net wrote:
On Monday 30 November 2009 18:16:50 Adam Williamson wrote:
Where I'm currently at is that I'm going to talk to some Red Hat /
Fedora security folks about
Although I have read all of the messages on this thread as of the date/time of
this message, I am replying to this first message with all of my comments.
My background: I am currently retired but a few years ago I was still being
paid the big bucks for working on computer security and security
On Wednesday 11 November 2009 06:41:58 Farkas Levente wrote:
On 11/11/2009 11:53 AM, Richard W.M. Jones wrote:
On Wed, Nov 11, 2009 at 10:14:21AM +, Richard W.M. Jones wrote:
echo input | time cpio --quiet -o -H newc /path/to/fs/output
Update: I found the -C option that lets me
Dnssec was introduced as a default in Fedora 11 and continues in Fedora 12.
The dnssec-conf package was introduced to modify/configure /etc/named.conf for
the dnssec support. Unfortunately, dnssec-conf (specifically /usr/sbin/dnssec-
configure has a significant problem. The problem is
