Re: F21 Self Contained Change: Security Policy In The Installer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2014-03-13 12:47 GMT+01:00 Jan Lieskovsky <jlieskov@xxxxxxxxxx>:
> There are many known tips and tricks how to make a system more secure, often
> depending on the use case for the system. With the OSCAP Anaconda Addon [1]
> and the SCAP Security Guide [2] projects, we may allow users choosing a
> security policy for their newly installed system.
>
> What is the proposed default configuration/policy?

FWIW WRT to scap-security-guide content there's only one (common) profile
at the moment. But it depends on the target group / volume / spin we would like
this to be by default part of -- once this is clear in that case the profile can
be adjusted / modified to prefer / select by default just rules intended for the
target group of that system

So, let me be more specific: If I install using the most default setup possible (not touching the policy spoke), will the installed system be affected by the policy / different from what is packaged in the RPMs?
    Mirek
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux