On Sun, 2008-04-06 at 15:32 -0400, Michael Stone wrote:
On Sun, Apr 06, 2008 at 01:11:55AM -0400, Polychronis Ypodimatopoulos wrote:
The SystemBus is used for communication between processes that belong to
different users. By default, /etc/dbus-1/system.conf says ...Deny
everything then
John (J5) Palmieri wrote:
Luckily all mail with DBus in the header gets filtered into a single
folder ;) Yes spoofing is the answer here (it is sort of like asking
why can't users create applications that run from /usr/bin though not
quite exact). If we allowed users to grab names on the
On Mon, 2008-04-07 at 10:57 -0400, Polychronis Ypodimatopoulos wrote:
John (J5) Palmieri wrote:
Luckily all mail with DBus in the header gets filtered into a single
folder ;) Yes spoofing is the answer here (it is sort of like asking
why can't users create applications that run from
John (J5) Palmieri wrote:
I can't think of a reason to want a system process invoking methods on a
user process.
Well, in my case, the system process is the only one having access to
the network and provides network connections and events to all user
processes. Sending signals to user
On Mon, 2008-04-07 at 11:43 -0400, Polychronis Ypodimatopoulos wrote:
John (J5) Palmieri wrote:
I can't think of a reason to want a system process invoking methods on a
user process.
Well, in my case, the system process is the only one having access to
the network and provides network
On Sun, Apr 06, 2008 at 01:11:55AM -0400, Polychronis Ypodimatopoulos wrote:
The SystemBus is used for communication between processes that belong to
different users. By default, /etc/dbus-1/system.conf says ...Deny
everything then punch holes Why do we forbid the default user
(olpc) by
I've been fiddling with DBus quite a bit lately and I don't really
understand its default security policy.
The SystemBus is used for communication between processes that belong to
different users. By default, /etc/dbus-1/system.conf says ...Deny
everything then punch holes Why do we forbid
