From: nicky726@gmail.com (Nicky726)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Basic policy for KDE and Konqueror
Date: Sun, 6 Sep 2009 14:22:27 +0200 [thread overview]
Message-ID: <200909061422.27551.Nicky726@gmail.com> (raw)
In-Reply-To: <mailman.3.1252170002.16620.refpolicy@oss.tresys.com>
Hello,
Dominick Grift wrote:
> looks like dbus_connect_session_bus() is not (yet) implemented in f11 and
> upstream refpolicy. Basically it facilitates the acquire_svc on user bus.
> You could create it yourself or add the local policy above as a workaround
> until the interface is implemented.
I'll use the workaround then, and when I have time, I'll try to look at
implementing the interface.
> The reason that dbus_connect_session_bus is not implemented is that
> confining GUI user apps does not have much priority and it presents some
> complications which minimize the benefits of confined gui user apps.
Could you write more about those complications which minimize benefits of
confined gui user apps? Or could you reffer me to some article?
Thanx for cooperation,
Ondrej Vadinsky
--
Don`t it always seem to go
That you don`t know what you`ve got
Till it`s gone.
(Joni Mitchell)
next parent reply other threads:[~2009-09-06 12:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1252170002.16620.refpolicy@oss.tresys.com>
2009-09-06 12:22 ` Nicky726 [this message]
2009-09-06 13:16 ` [refpolicy] Basic policy for KDE and Konqueror Dominick Grift
2009-09-05 15:39 Nicky 726
2009-09-05 15:48 ` Dominick Grift
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 14:52 Nicky 726
2009-09-04 15:19 ` Dominick Grift
2009-08-12 12:40 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
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
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=200909061422.27551.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.