Hi,
I'm planning a service with a login-user-interface. Thus, I want to restrict
the user somehow to this script and to do nothing else.
The straight-forward way would be to write this script, have all input parsed
by read and then let the script act according to this input (let's assume
that
...@freebsd.org owner-freebsd-questi...@freebsd.org
To: freebsd-questions@freebsd.org freebsd-questions@freebsd.org
Sent: Thu Nov 18 07:52:39 2010
Subject: Escaping from shell-scripts
Hi,
I'm planning a service with a login-user-interface. Thus, I want to restrict
the user somehow to this script
Julian Fagir wrote:
Hi,
I'm planning a service with a login-user-interface. Thus, I want to restrict
the user somehow to this script and to do nothing else.
The straight-forward way would be to write this script, have all input parsed
by read and then let the script act according to this input
On Thu, 18 Nov 2010, Julian Fagir wrote:
Hi,
I'm planning a service with a login-user-interface. Thus, I want to restrict
the user somehow to this script and to do nothing else.
The straight-forward way would be to write this script, have all input parsed
by read and then let the script act
On Thu, Nov 18, 2010 at 8:52 AM, Julian Fagir g...@physik.tu-berlin.dewrote:
Hi,
I'm planning a service with a login-user-interface. Thus, I want to
restrict
the user somehow to this script and to do nothing else.
The straight-forward way would be to write this script, have all input
doug d...@fledge.watson.org writes:
If you make a program a shell AFAIK to escape is to logff. Bash has a
chroot like facility that might work. However if you write a simple C
program as a wrapper for your shell script and make that program a
shell, I would think that is pretty secure.
As
On Nov 18, 2010, at 5:52 AM, Julian Fagir wrote:
The straight-forward way would be to write this script, have all input parsed
by read and then let the script act according to this input (let's assume
that these tools are secure, it's just cp'ing and writing to
non-sensitive files.
Are
