On Jan 3, 2011, at 1:22 PM, eveningnick eveningnick wrote:
>> Unless I'm forgetting something basic, you should be able to connect to your
>> daemon's socket from a non-root process if you first change the permissions
>> on the socket (using chmod, as if it were a file). The man page for the
>>
On Mon, Jan 3, 2011 at 1:22 PM, eveningnick eveningnick
wrote:
> I dont want everyone to be able to write to that socket, the point is
> to let only System Preferences (for example, by displaying
> "Autorization dialog box" - like "User Accounts" preference pane, for
> example.
> I am wondering if
> Unless I'm forgetting something basic, you should be able to connect to your
> daemon's socket from a non-root process if you first change the permissions
> on the socket (using chmod, as if it were a file). The man page for the
> unix-domain protocol family alludes to this briefly:
>
>> All a
On 3 Jan 2011, at 11:03 AM, eveningnick eveningnick wrote:
> i have a daemon whose owner is wheel:root and which provides a Unix
> Domain Socket where i can send/receive datagrams from my custom
> Preference Pane.
> The problem i have is that a socket, installed by a root-process can't
> be "sent"
Hello
i have a daemon whose owner is wheel:root and which provides a Unix
Domain Socket where i can send/receive datagrams from my custom
Preference Pane.
The problem i have is that a socket, installed by a root-process can't
be "sent" by a non-root application, like System Preferences.
I guess i
