Alexander Blach

This is the verbose output of the failing FTP upload command that eventually times out and results in a 0 byte file on the server: ``` * Connected to .kasserver.com...

The problem might be related to https://github.com/curl/curl/issues/6149 This issue was actually discovered when using libcurl to upload a file >18KB using FTP with explicit auth SSL to that server. With...

I just set up a brand new vsftpd server on a Debian 12 machine that is publicly accessible. I created a new RSA 4096 key and enabled SSL for the...

The redacted commands to reproduce this after setting up the vsftpd server with SSL are: To create a local file with a size of 18 kB: `head --bytes 18432 /dev/zero...

I also asked the support team at all-inkl.com what FTP server software they are using. They answered that they are using ProFTPD from the original Ubuntu repository. So it looks...

Can you reproduce this issue? Is there anything I can do to help?

I just added `require_ssl_reuse=NO` to `/etc/vsftpd.conf`, restarted the vsftpd service and ran the upload command again. I see no difference in behavior. It still results in a 0 byte file...

> @blach could you add `-v --trace-config ids,time,tcp,read` and tell use what gets logged? Here is the log: ``` > curl --ssl-reqd --insecure ftp:/// -u demo: --upload-file test-curl.txt -v --trace-config...

Some additional details: I just tried running the curl command on the server that runs the vsftpd server. The server runs Debian 12.5 Bookworm which comes with curl 7.88.1. Curl...

Could this be an aarch64 vs x86_64 architecture issue?