From: nicky726@gmail.com (Nicky726)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Basic policy for KDE and Konqueror
Date: Thu, 27 Aug 2009 18:07:52 +0200 [thread overview]
Message-ID: <200908271807.52210.Nicky726@gmail.com> (raw)
In-Reply-To: <1250103483.19221.31.camel@notebook2.grift.internal>
Helo,
I managed to implement almost all of your comments to KDE and Konqueror
policy. Now I need to do some testing, which is where I got totaly stuck.
First to the konqueror_role(). I created this interface according to policy
for mozilla, but i quite don't get it, where should I place the call itself.
You mention userdomain policy:
Dne St 12. srpna 2009 20:58:03 Dominick Grift napsal(a):
> the konqueror_run interface calles should be replaced by
> konqueror_role() calls. These calls do not belong there but they belong
> in the user domain policy.
But I didn't find there much xxx_role() calls. More important I didn't find
there any mozilla_role() which I take as a reference. When I looked through
refpolicy sources I managed to find mozilla_role() and other xxx_role() calls
in roles/unprivuser.te and other roles. So to where do these calls belong?
I am not sure, that I fully comprehend this situation concerning xxx_role()
calls. I had interface konqueror_run() which was called in konqueror.te. This
should now be replaced by konqueror_role() which I guess should do something
similar, and be called where? What is it good for? And are there more changes
needed so it worked? Could someone explain this more?
Now to the testing stuff. Til now I managed to test the modules against
unmodified Fedora targeted policy. But with konqueror_role() calls there are
some modifications needed. How to do it? I didn't have much luck with inserting
changed modules to fedora policy, nor with compling what I hope was exact copy
of fedora policy.
I also think, that this module should be tested against refpolicy-git
shouldn't it? The problem with this is, that fedora didn't even booted with
git refpolicy. How do you test the modules than?
Thanks for the answers,
Ondrej Vadinsky
next prev parent reply other threads:[~2009-08-27 16:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 12:40 [refpolicy] Basic policy for KDE and Konqueror Nicky726
2009-08-12 18:58 ` Dominick Grift
2009-08-17 14:40 ` Nicky726
2009-08-17 15:01 ` Mike Edenfield
2009-08-27 16:07 ` Nicky726 [this message]
2009-08-27 16:42 ` Dominick Grift
2009-08-27 16:47 ` Dominick Grift
2009-09-03 20:15 ` Nicky726
2009-09-03 20:36 ` Dominick Grift
2009-08-14 17:37 ` Christopher J. PeBenito
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 14:52 Nicky 726
2009-09-04 15:19 ` Dominick Grift
2009-09-05 15:39 Nicky 726
2009-09-05 15:48 ` Dominick Grift
[not found] <mailman.3.1252170002.16620.refpolicy@oss.tresys.com>
2009-09-06 12:22 ` Nicky726
2009-09-06 13:16 ` Dominick Grift
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908271807.52210.Nicky726@gmail.com \
--to=nicky726@gmail.com \
--cc=refpolicy@oss.tresys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.