Core FTP

currently there is only the "FIPS mode" option, which will prevent most outdated algorithms/ciphers from being used..

Will look into the possibility of being able to select ciphers

In the domain setup under "Disable FTP" - "..." there are options to disable SSL and check TLS versions to use. Changes go into effect next server restart.

--------

Cumulative updates from builds 772-774

Additional speed improvements

A fix for this issue will be build 775.

To get around this issue, "Start" Core FTP Server and then registration should proceed to work correctly.

If this does not work, contact support for the stand-alone registration utility

---------------

--------------------

--------------------

It looks like the client may have aborted the transfer as a disconnection was likely the reason for the abort of the transfer by Core FTP Server.

Would check the client for any potential error messages that may help diagnose the issue.

----------------

----------------------

---------------------

Uncheck the "PASV" command in your site profile

The mini server does *not* utilize libssh - it is not used in Core FTP mini server

What would be needed is a test demonstrating that the same issue occurs with the mini server to verify this issue actually exists.

This looks to be a libssh issue and may not apply to Core FTP software.

If there is an example of this bypass, please forward to feedback at coreftp.com

-key <c:\path\keyfilename>

In looking at the error it looks like the site profile is not being found as the hostname isn't correct. If you switch to "file based storage" it will likely alleviate these issues.

https://coreftp.com/forums/viewtopic.php?t=4022670

Build 770 may fix this issue that was introduced in build 761.

Cumulative updates from builds 764-770

Fixes an error introduced in 2.34 that may have caused stat issues for some clients.

The user may be exceeding the "max conns per IP" setting. You can increase it on a per user basis in the user's "general" - "limit # of logins" setting.

There is also the "Always allow login" option also but use with caution.

----------

A recent test with the import function reveals some issues that are fixed as of build 769.

-----------------------

---------------

................

---------------

1) -c config.json (does this need a full path?)

2) Try the call without the cmd.exe /c portion.

3) echo %ProgramFiles% out to a file to verify the environment variable is accurate.

If none of these helps then this will be tested further.

There is a global option (view - options - view/edit), "Update edited files on save".

If checked (may require restart), does it change the behavior?

------------------

-----------------

--------

------------------------

Cumulative updates from builds 753-761

This seems to only apply to Linux. Wouldn't be concerned until it is replicated in Windows.

CVE-2024-6387

The reason to use PGP is so nobody but the intended end user can access a file because it is encrypted.

PGP shouldn't be used on the server, its essentially removing the security it provides.

Try unchecking the "PASV" option. If that doesn't work, post the client log showing the error.

----------------

------------------------------

Option added to build 1987 and greater

Install right over your existing setup. As of this post all versions use the same configuration data. Before installing you can backup the following settings for peace of mind: CoreFTPServer\config.dat CoreFTPServer\certs\ -- (copy entire directory, location may also vary, and can be retrieved from ...

--------------------------

Search found 968 matches