From: Quentin Glidic sardemff7+...@sardemff7.net
Signed-off-by: Quentin Glidic sardemff7+...@sardemff7.net
---
This patch restores the old behaviour if the user wants to. This keeps
/bin/sh around for shells that do not understand -c weston \$@\.
src/weston-launch.c | 10 --
1 file
Where is the shell coming from? If it's the shell specified in /etc/paswd
and if we can guarantee that it doesn't read ~/.profile or similar than
it's ok. However, If this is the case, then how is it useful to run with
the user's shell?
If it is the shell from $SHELL or if it reads ~/.profile
Hi,
On 24/01/2014 08:33, David Herrmann wrote:
weston-launch passes privileged FDs back to weston. I don't think we
should allow a user to use their own shell to spawn weston. How can
you guarantee the shell does not point to some random binary of the
user? This way, they can get access to
