SFTP Archives - File transfer tool from Limagito

08 Jun
How to use domain account authentication in our SFTP and FTP server
How to use domain account authentication in our SFTP and FTP server
In version v2025.6.8.0 we added the possibility to use domain users as authentication method.
Select Server menu item > SFTP Server
There are a couple of ways to use this new ‘Domain User’ option. The examples below are related to SFTP but the same counts for FTP(S).
1. First example:
Domain User is enabled
Username is set to “administrator”
You need to use the sAMAccountName
Domain Name is set to “limagito”
When a SFTP client connects to our SFTP server with the user “administrator” we will request the domain “limagito” to check if the provided password from the SFTP client is correct.
2. Second example:
Domain User is enabled
Username is set to “limagito\administrator”.
The Username is prefixed by the domain.
You need to use the sAMAccountName
Domain Name is left blanc
When a SFTP client connects to our SFTP server with the user “limagito\administrator” we will request the domain “limagito” to check if the provided password from the SFTP client is correct.
3. Third example:
Domain User is enabled
Username is set to “localhost\administrator”.
The Username is prefixed by the domain.
You need to use the sAMAccountName
Domain Name is left blanc
When a SFTP client connects to our SFTP server with the user “localhost\administrator” we will request the localhost user accounts to check if the provided password from the SFTP client is correct.
In this version we also added a LDAP(S) client option. In the first two account examples we used the “limagito” domain. Our domain LDAPS server is listening on IP 192.168.2.202 – Port 636.
Check ‘Enable LDAP Client(s)’
Add the Client(s) you need
You can add multiple domains
For each domain you add, you need to add:
LDAP Host, our LDAP test server is using the IP 192.168.2.202
LDAP Port, our LDAP test server is listening on Port 636
LDAP Use TLS
When enabled TLS will be used to encrypt the LDAP packets
If you need any help with this ‘domain account authentication’ option, please let us know.
Best Regards,
Limagito Team
#sftp #ldap #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team FTP LDAP SFTP domain, LDAP
03 Mar
Complete rewrite of our Limagito SFTP server in v2025
V2025.3.2.0 contains a complete rewrite of our Limagito SFTP Server
We completed the rewrite of our previous server code. We have never been 100% ok with the previous third party code provider. In this build we switched to SecureBridge from Devart as new third party code provider .. what a difference!
Common features
Full support for the SSH2 protocol
SFTP V3 up to v6
Authentication by password or public key
Support for most SSH2-compatible clients including OpenSSH
Robust protection against different kinds of cryptographic attacks
Fast and customizable
External modules are not required
Algorithms support
Support for AES128, AES192, AES256, Blowfish, Cast128, and TripleDES symmetric algorithms
Support for SHA-2, SHA-1, and MD5 hashing algorithms
Support for Elliptic-Curver, RSA and DSA asymmetric HostKey algorithms
Reliable and convenient storage, transfer, and verification of asymmetric keys

The following Ciphers, HMAC and Key Exchange Algorithms are available in the new version:
Server Setup:
User Accounts Setup:
User Account Permissions Setup:
HostKey Setup:
Logging Setup:
If you need any help regarding this new Limagito SFTP server, please let us know.
Best Regards,
Limagito Team
#SFTP #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team SFTP sftp server
12 Oct
SFTP Fingerprint option added to Limagito file mover
Q: I have a question related to SFTP fingerprints. When I create a new rule and add new Source -> SFTP, where can I configure the fingerprints of the Source host’s fingerprint? I would like to be sure that the server is valid.
A: We allow the fingerprint of the sftp server you added as source automatically. At this moment there is no option to add fingerprints of the host manually.
Q: Thanks for the very quick answer. Hopefully it will be possible on the next version. There is a possibility for MiTM attack.
A: In version v2024.10.12.0 we added the Fingerprint option for SFTP as Source and Destination.
The goal of the fingerprint is to verify the authenticity and integrity of the SFTP server you’re connecting to. This is a short, unique representation (a hash) of the server’s public key. The purpose of this fingerprint is to help you confirm that you’re connecting to the correct server and not a malicious or imposter server. This is optional and by default we allow any fingerprint.
E.g.
The default Hash Algorithm is MD5
68:ff:d1:4e:6c:ff:d7:b0:d6:58:73:85:07:bc:2e:d5
Please add one if the following prefixes to adjust the default Hash Algorithm:
SHA256:
SHA384:
SHA512:
SHA1:
SHA3-224:
SHA3-256:
SHA3-384:
SHA3-512:
In case you receive an error message regarding the Fingerprint Compare, please increase the RunTime Log Level to ‘Debug’:
RunTime Log example:
If the the fingerprint in your SFTP setup is not correct, the following error message will appear
Increasing the log level of the RunTime log will show you the Fingerprint the SFTP server is sending
You can compare this to the one in your setup, in the example below we used the SHA256 hash algorithm
If you need any help with this request, please let us know.
Best Regards,
Limagito Team
#sftp #managedfiletransfer #filetransfer #filemanagement
By Limagito-Team SFTP fingerprint, SFTP