Ftp 426 ошибка

After upgrading vsftpd to version 3.0.5-48.3.1, many FTP clients increasingly report the following error, typically at the end of a file upload from a client.

  426 Failure reading network stream.

Some attempts work, some do not.  It happens with a variety of clients.

Set this parameter in /etc/vsftpd.conf:

strict_ssl_read_eof=NO

According to the vsftpd.log during these events, this condition also existed at the time of the error:

"DATA connection terminated without SSL shutdown"

This means that the client tried to terminate a TCP connection which was using SSL, but did not send an SSL_SHUTDOWN first.  This is improper SSL behavior from the client side and is very common..

When this happens, if vsftpd is being strict about ssl behavior (controlled by configuration parameter «strict_ssl_read_eof‘»), it will return the 426 error to the client.

According to the man page for vsftpd.conf, this should be disabled per default:

strict_ssl_read_eof
     If enabled, SSL data uploads are required to terminate via SSL,
     not an EOF on the socket. This option is required to be sure
     that an attacker did not terminate an upload prematurely with a
     faked TCP FIN. Unfortunately, it is not enabled by default
     because so few clients get it right. (New in v2.0.7).

    Default: NO 

However, in the code it’s enabled by default: 
tunables.c:225:  tunable_strict_ssl_read_eof = 1;

The man page needs to be updated to show the correct default.  This has already been updated upstream by the Linux community, but that update has not yet reached the vsftpd package in SLES 12 SP5.

32

11 мая 2010, 12:30

3182

Добрый день!

ФТП клиенты(разные) на различных хостингах после некоторого времени работы начинают выдавать 426 ошибку. Из-за этого не получается сохранить (и пересохранить) файлы. Понял, что проблема на стороне клиента, т.е. на моей — но как побороть, кроме как ребутнуться, так и не могу разобраться:(

Если кто-то знает, как решить — помогите пожалуйста!

• Помощь в фильтрации ботов через CloudFlare
• Резкий спад трафика на сайте
• Помогите разобраться как фиксить количество процессов web-сервера

[Удален]

11 мая 2010, 13:49

#1

69

11 мая 2010, 13:54

#2

426 — Канал закрыт, обмен прерван

А порыться нельзя?

Скорее всего, проблема у тебя в файрволлинге. или же, если ты пользуешь nat для выхода инет, то тебе просто необходимо указать клиенту использовать passive mode (pasv);)

An FTP 426 reply code will be issued by the FTP server on the IBM® System i® products if the file
receiving the data from the PUT or MPUT command is too small to receive all of the data. You will see a
message on your client within your FTP sessions similar to one of the two following messages:

426 — Unable to close file CPE3101.
or
426 — Cannot write to member xxxxxx in file yyyyyy in library zzzzzzz.

For all file types, do the following:
1) Increase the size of the file on the server system.

2) Verify the user profile that creates or sends the file has the Maximum Storage parameter set to a large
enough value.

3) Reduce the size of the file that is being sent to the server system.

4) If the file is a flat file, ensure the file is not already created on the target system.

If the file is a save file, do the following:
1) Re-create the target save file.

2) This message also indicates that records are out of order in the save file. This often happens if the
save file was transferred to a system that is not a System i. In this case, the save file must be
re-created or retransferred from the source.

3) Examine the Maximum Storage Allowed parameter of the user profile that owns the save file on the
target system. This storage determines how big the file can be, and it will cause this error.