weston-launch logging and security (Re: [PATCH weston] weston-launch: Print explanation of why we failed to open the device)

[Pekka Paalanen]

On Mon, 20 May 2013 16:56:47 -0400
Kristian Høgsberg <hoegsberg at gmail.com> wrote:

> On Mon, May 20, 2013 at 04:55:10PM +0100, Rob Bradford wrote:
> > From: Rob Bradford <rob at linux.intel.com>
> 
> That's better, though I wonder if we should instead let weston log the
> error message using weston_log()... committed this for now.

That was my first thought, too. Just send errno from weston-launch,
or/and message string?

Would be nice to have all that in weston's log.

What about syslog in addition? weston-launch is a suid-root program,
so might be useful to log into system log for security purposes, no?
PAM is writing its own stuff to the system log on behalf of
weston-launch already.

Btw. if we have a mechanism for weston to load custom plugins, then
those plugins could ask weston-launch to open any file with root
permissions, right? Do we have any restrictions in opening or plugin
loading yet?


Thanks,
pq