My Life

System: Fedora Core 5, with all updates. vsFTP version: 2.0.4, but at the time of writing this, the latest version is 2.0.5 Scenario: Config to allow BOTH real account and anonymous account come in. Concept: My through is: if we allow both real and anonymous account come in, first anonymouse_enable=YES and local_enable=YES, write_enable=YES also. For security reason, chroot_list shoule be YES and add a chroot_list file also. For the same reason, user_list should be YES and add a user_list file also. Here comes to the hard part: - Assume that the default ftp folder is /var/ftp, inside this folder there is a folder call pub - Assume also that there is another folder called /home/myFTP, which is a home folder for user: myFTP. BY DEFAULT, /home/myFTP can only be accessed by myFTP only. i.e. file user and group are both: myFTP If I want to access /home/myFTP through FTP, first mount the folder: mount --bind /home/myFTP /var/ftp/pub The above command means: when I accessd /var/ftp/pub,

Scenario: Your boss required you to establish one FTP account for a group of people to use in a project. The account used by these people is read only. The file structure of IIS FTP is as follow: C:\Intepub | |---ftproot | |---FTPUserA |---FTPUserB |---(NewFTPAccountForThisProject - All files should be read only here.) The steps are as follow: 1) In W2K3, create a user named 'proj' and corresponding password. 2) Under ftproot, create a folder called 'proj', which is the SAME NAME as the user you created before. 3) Here comes to the hard part: In 'ftproot', user rights of 'proj' should be assigned to: read only. i.e. in 'Security' tab, user 'proj' should be added and only 'read' is checked, other rights are left unchecked. In 'proj' folder, remove all default users in 'Security' tab > add back 'administrators' and 'proj' > &#

After you installed spamassassin through either perl or tar, you may want to test your spamassassin by issuing the following command: #> spamc -R < Your_test_message However, what you get is just: 0/0 According to spamassassin documentation, it is caused by "error".... but the point is, what is this error? How did it come from? One of the reason for this error may be caused by: you haven't start your spamd: To start spamd explicitly, type: #> spamd& The '&' sign means to put 'spamd' run in the background. Once I typed this command and issue the spamc command again, it works: #> spamc -R < Your_test_message So, if you want to use spamassassin, please make sure you start your spamd first before testing spamc.

To block/deny root login in ssh, do the following (under FC4/5) 1.>vi /etc/ssh/sshd_config 2.Find the line: #PermitRootLogin yes Uncomment this line and change the word 'yes' to 'no' as follow: PermitRootLogin no 3.Restart SSH: /etc/init.d/ssh restart Finished! Although user cannot login as root directly through SSH, they can login as normal user and 'sudo su -' to login as root. Please be careful.