FTP-related configuration and memo

1. vsftpd 530 login incorrect.

This problem found many resources on the Internet, and Google finally found a feasible solution when searching 6th pages.

Configure the path of the/etc/PAM. d/vsftpd file to the real path of the dynamic library. If the file does not exist, see the file in the vsftpd installation path or the following content:

#%PAM-1.0auth       required     /lib64/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeedauth       required     /lib64/security/pam_unix.so shadow nullokauth       required     /lib64/security/pam_shells.soaccount    required     /lib64/security/pam_unix.sosession    required     /lib64/security/pam_unix.so

My symptom is that you can log on anonymously, but you cannot log on using system users. There are many online solutions, but most of the problems are concentrated on Pam (Pluggable authorization manager. I used the PAM file,/etc/PAM because I used a 64-bit system. the module path in the D/vsftpd file is the/usr/lib/PAM _ * directory. If you find it online, you can use the relative path, that is, remove the preceding path. This reminds me of the differences in the system. I checked that there are many modules in/usr/lib64, and there is only one file in/usr/lib, this is the key to this issue.

The name of the PAM file must be the same as that of pam_service_name. Some netizens say that the absolute path is required. This may be related to the configuration. You can try it. The absolute path is absolutely correct.

For external access, you need to pay attention to the firewall on Linux and related SELinux.

2. Serv-U uses the Chinese path and Chinese file name

Serv-U supports utf8 encoding in the path, which is usually the default configuration. If the FTP client does not use utf8 encoding, the correct Chinese path resolution may not be obtained, if you use a client such as the open-source Apache package ftpclient, You need to convert the encoding to utf8 to view the Chinese path. When uploading a Chinese path or file name, you also need to convert the encoding, unless your project uses utf8 encoding by default.

There are two ways: (a) modify the server configuration (B) send the command "opts utf8 off" to disable utf8 resolution"

3. vsftpd uses a Chinese path and a Chinese file name

Vsftpd supports opts utf8 on. If "always support utf8" is returned for this name, the command is not recognized when "opts utf8 off" is used. It can be seen that there is a difference between this and Serv-U. I use utf8 encoding on Linux, and the transmission cannot make it possible to view the Chinese file name, however, in the GBK environment, we can see that the Chinese name of GBK is used. I guess it may be because of the font, And the utf8 Chinese encoding cannot be correctly displayed.

The method I used is to use GBK, that is, lang = zh_cn.utf8, and control terminal encoding, that is, ftpclient, for uploading. the getcontrolencoding () function is used to convert the file name encoding. After the file is uploaded, Chinese characters can be recognized on Linux and can be recognized on IE and Firefox. The encoding is gb2312.

4. Failed to access vsftpd in IE

In my experiment, I found that IE only supports the ASCII mode, while vsftpd disables the ASCII mode by default, while Firefox does allow access in the ASCII mode, and when ie accesses, in passive mode, public IP addresses cannot be used, that is, routes are not supported. Because my environment is:

The public IP address accesses ftp. in passive mode, the IP address returned to the client is an intranet IP address, which cannot be accessed by IE, but can be accessed by Firefox. (I am speechless with IE ).

Note that if IE accesses the vsftpd server with a public IP address and an error occurs, the vsftpd server will be suspended and must be restarted !!! This is a disgusting ie! I suspect that an error occurs when Internet and Intranet IP addresses are accessed by Internet Explorer, and the FTP passive port of the server is occupied, causing the server to fail.

5. 425 security: Bad IP connection

This error occurs when the public IP address and the Intranet IP address access the vsftpd server, and the server sets the IP check mechanism. Modify the pasv_promiscuous = yes in the/etc/vsftpd. conf file.