Hi Ralf!
2. chroot everything
just chroot the users at the login after ssh (if you want to allow ssh),
How can chroot a user who logs in via ssh? Do you have some links about
this?
--
Sebastian Schinzel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Quoting Sebastian Schinzel [EMAIL PROTECTED]:
Hi Ralf!
2. chroot everything
just chroot the users at the login after ssh (if you want to allow ssh),
How can chroot a user who logs in via ssh? Do you have some links about
this?
--
Sebastian Schinzel
Hello,
I'm helping someone to install a webserver, and we're trying to make it
a little secure. It's a Woody with Apache 1.3.26 and PHP 4.1.2. For the
users we have a ProFTPd with mod_sql (the users are in the database).
Currently all the site are set to user www-data and when the user access
Hi,
StarK wrote:
What kind of security can I use to avoid this ? Can we chroot the PHP
(Yes I know it's a strange sentence :) ?
i know two useable solutions:
1. care about every service:
use SuEXEC for CGIs, Safe Mode for PHP, a good directory and right
structure.
2. chroot everything
On Tue, Jul 23, 2002 at 03:31:20PM +0200, Ralf Dreibrodt wrote:
What kind of security can I use to avoid this ? Can we chroot the PHP
(Yes I know it's a strange sentence :) ?
1. care about every service:
use SuEXEC for CGIs, Safe Mode for PHP, a good directory and right
structure.
A
5 matches
Mail list logo