chroot_list_enable 
YES に設定した場合、ログイン後にホームディレクトリへと chroot() されるローカルユーザのリストを指定できる。 chroot_local_user を YES に設定した場合には、意味が異なってくる。 リストはその場合、chroot() jail へと移動されないユーザ のリストとなる。 デフォルトでは、このリストは /etc/vsftpd.chroot_list ファイルであるが、 chroot_list_file 設定によってこれを変更することができる。 
デフォルト: NO
# (default follows)
#chroot_list_file=/etc/vsftpd/chroot_list

chroot_local_user 
YES に設定した場合、ローカルユーザは(デフォルトで)ログイン後に ホームディレクトリへと chroot() される。 警告: このオプションはセキュリティに密接に関連する。 ユーザがアップロード権限を持っていたり、シェルでのアクセスができる場合は 特にである。 何をしているかを理解している場合にのみ有効にすること。 これらのセキュリティの問題は vsftpd に特有の問題ではないことに 注意してほしい。 ローカルユーザを chroot() jail に入れることができるすべての FTP デーモンにおいて、この問題がある。
デフォルト: NO

vi /etc/vsftpd/vsftpd.conf

# When "listen" directive is enabled, vsftpd runs in standalone mode and
# listens on IPv4 sockets. This directive cannot be used in conjunction
# with the listen_ipv6 directive.
# Start wuth xinetd
#listen=YES

/etc/init.d/vsftpd stop

# vi /etc/xinetd.d/vsftpd
service ftp
{
　　disable = no
　　socket_type = stream
　　wait = no
　　user = root
　　server = /usr/sbin/vsftpd
　　server_args = /etc/vsftpd/vsftpd.conf
　　log_on_success += DURATION USERID
　　log_on_failure += USERID
　　nice = 10
}

/etc/init.d/xinetd restart

# whereis sshd
/usr/sbin/sshd 

# vi /etc/xinetd.d/sshd
service ssh
{
        disable         = no
        socket_type     = stream
        wait            = no
        user            = root
        server          = /usr/sbin/sshd
        server_args     = -i
        log_on_success  += DURATION USERID
        log_on_failure  += USERID
        nice            = 10
}

/etc/init.d/sshd stop
/etc/init.d/xinetd restart
chkconfig sshd off

# diff -Nur old_kernel_kuduzu new_kernel_kuduzu
--- old_kernel_kuduzu   2009-02-02 11:08:19.000000000 +0900
+++ new_kernel_kuduzu   2009-02-02 10:44:47.000000000 +0900
・・・・・・・・・・・・
・・・・・・・・・・・・
@@ -490,15 +492,14 @@
 pcidom:    0
 pcibus:  4
 pcidev:  0
-pcifn:  0
+pcifn:  1
 -
-driver: e1000
+driver: e1000e
 desc: "Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper)"
-network.hwaddr: 00:1f:d0:ae:0d:4a
 vendorId: 8086
 deviceId: 1096
 subVendorId: 1458
@@ -490,15 +492,14 @@
 pcidom:    0
 pcibus:  4
 pcidev:  0
-pcifn:  0
+pcifn:  1
 -
 class: NETWORK
 bus: PCI
 detached: 0
 device: eth1
-driver: e1000
+driver: e1000e
 desc: "Intel Corporation 80003ES2LAN Gigabit Ethernet Controller (Copper)"
-network.hwaddr: 00:1f:d0:ae:0d:4b
 vendorId: 8086

[nininini@wwwdb mysql]$ mysql_secure_installation 
 
 
 
 
NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL
      SERVERS IN PRODUCTION USE!  PLEASE READ EACH STEP CAREFULLY!
 
 
In order to log into MySQL to secure it, we'll need the current
password for the root user.  If you've just installed MySQL, and
you haven't set the root password yet, the password will be blank,
so you should just press enter here.
 
Enter current password for root (enter for none): 
OK, successfully used password, moving on...
 
Setting the root password ensures that nobody can log into the MySQL
root user without the proper authorisation.
 
You already have a root password set, so you can safely answer 'n'.
 
Change the root password? [Y/n] n
 ... skipping.
 
By default, a MySQL installation has an anonymous user, allowing anyone
to log into MySQL without having to have a user account created for
them.  This is intended only for testing, and to make the installation
go a bit smoother.  You should remove them before moving into a
production environment.
 
Remove anonymous users? [Y/n] y
 ... Success!
 
Normally, root should only be allowed to connect from 'localhost'.  This
ensures that someone cannot guess at the root password from the network.
 
Disallow root login remotely? [Y/n] y
 ... Success!
 
By default, MySQL comes with a database named 'test' that anyone can
access.  This is also intended only for testing, and should be removed
before moving into a production environment.
 
Remove test database and access to it? [Y/n] y
 - Dropping test database...
 ... Success!
 - Removing privileges on test database...
 ... Success!
 
Reloading the privilege tables will ensure that all changes made so far
will take effect immediately.
 
Reload privilege tables now? [Y/n] y
 ... Success!
 
Cleaning up...
 
 
 
All done!  If you've completed all of the above steps, your MySQL
installation should now be secure.
 
Thanks for using MySQL!
 
 

# yum list
Loading "rhnplugin" plugin
Loading "security" plugin
This system is not registered with RHN.
RHN support will be disabled.
Installed Packages
Deployment_Guide-en-US.noarch            5.2-9                  installed       
Deployment_Guide-ja-JP.noarch            5.2-9                  installed       
GConf2.i386                              2.14.0-9.el5           installed       
GConf2-devel.i386                        2.14.0-9.el5           installed       
ImageMagick.i386                         6.2.8.0-4.el5_1.1      installed       
MAKEDEV.i386                             3.23-1.2               installed       
…

# yum check-update
Loading "rhnplugin" plugin
Loading "security" plugin
This system is not registered with RHN.
RHN support will be disabled.
Skipping security plugin, no data
Skipping security plugin, no data
Skipping security plugin, no data