I'm trying to establish a jail on a FBSD 6.1 system and have a couple of questions on bringing up the daemon.
Under the jail man page there are two user flags that I am unclear on,
-u username The user name from host environment as whom the command
should run.
-U... (1 Reply)
I was reading an article on how it is very important to setup a chroot jail to run bind. I can follow what the article says but one thing I am unclear about is now on system boot the BIND process in the chroot jail will start since it the owner will no longer be root but some other user. Can... (1 Reply)
Hi Gurus,
I am creating a user for ftp only on Solaris 10. However while testing I can see user can reach to root directory.
I followed following while creating the user
1 Created a shell in /usr/bin/ftponly as chmod a+x to ftponly
2 Placed the entry in /etc/shells
... (2 Replies)
I have a developer that needs ssh access to a server to get to a specific directory. I want to restrict them to that directory. I've tried to set their shell as rksh which does jail them but only if they are using ssh from another unix system. If they are using putty or winscp they can still... (2 Replies)
Hi, I was wondering if you can help me with verifying if certain extension exists in /var/log with an if statement. Basically I'm trying to see if there is a .Gz extension in the repertory /var/log.
My code:
if ; then
echo ¨ The extension exist¨
else
echo ¨theres no extension¨
fi
... (2 Replies)
Hello people,
I'm creating a web game control panel, where people can manage their gameserver on a php made control panel.
But i have no idea how to create an jailed inviroment for the gameserver,
I've looked at possebilites for chroot, but i don't want the gameserver has any binaries of linux... (1 Reply)
Discussion started by: gm33
1 Replies
LEARN ABOUT HPUX
chroot
chroot(1M)chroot(1M)NAME
chroot - change root directory for a command
SYNOPSIS
newroot command
DESCRIPTION
The command executes command relative to the newroot. The meaning of any initial slashes in path names is changed for command and any of
its children to newroot. Furthermore, the initial working directory is newroot.
Note that command suffixes that affect input or output for the command use the original root, not the new root. For example, the command:
locates file relative to the original root, not the new one.
The command variable includes both the command name and any arguments.
The new root path name is always relative to the current root. Even if a is currently in effect, the newroot argument is relative to the
current root of the running process.
This command is restricted to users with appropriate privileges.
EXTERNAL INFLUENCES
International Code Set Support
Single- and multibyte character code sets are supported.
WARNINGS
command cannot be in a shell script.
Exercise extreme caution when referring to special files in the new root file system.
does not search the environment variable for the location of command, so the absolute path name of command must be given.
When using to establish a new environment, all absolute path name references to the file system are lost, rendering shared libraries inac-
cessible. If continued access to shared libraries is needed for correct operation, the shared libraries and the dynamic loader be copied
into the new root environment.
SEE ALSO chdir(2), chroot(2).
STANDARDS CONFORMANCE chroot(1M)
12-12-2011
