On 2/25/11 2:04 AM, "Rolf Offermanns" <[email protected]> wrote:

>Hi All,
>
>can someone please help me understanding a few things:
>
>The security framework is supposed to be part of MeeGo 1.2.
>
>Is this still true?

There are a number of different pieces that have already been included in
our Trunk.


>Will it be in MeeGo core or just in one (or more) verticals?

The intent is to have these as a part of core so they can be leveraged by
the verticals that have more stringent security requirements.


>If I understood the conference videos and paper correctly, several
>packages will have to be modified so that they come with MANIFEST files
>and other metadata used by the package manager to setup things correctly.
>
>However from what I can see in the current nightly build there are no
>MANIFEST files in the rpms. I admit I did check only a few.

The intent is for 1.2 to have a permissive security model.  I did not
think that it would be possible to get all of the packages to include
manifest files in time for the 1.2 release.  Critical components with
security implications will be including appropriate manifest files for
1.2.  The current plan is to require all packages have manifest files for
the 1.3 release.


>Is there already a (test-)package which can be used to see/feel how
>things will work?
>
>In addition SMACK is not enabled in the default kernel package either.
>
>Correct?

Currently, the reference kernel does not have SMACK enabled.  There are
some specific adaptation kernels that are including it.  For 1.3, the
intent is to flip that around; have SMACK on in the reference kernel and
then turn it off in adaptation kernels that don't require it.


>When will this be added to the build? (please a little bit more specific
>than "soon" ;) Do you have a roadmap for it?

Smack patches were submitted to the MeeGo-Kernel mail list earlier this
month.


>MeeGo 1.2 is in freeze right now, so how will you get all of this
>included?

We're working with the CCB to get these in.

Ryan


_______________________________________________
MeeGo-security-discussion mailing list
[email protected]
http://lists.meego.com/listinfo/meego-security-discussion

Reply via email to