SFTP Archives - Page 2 of 4 - File transfer tool from Limagito

27 Jun
Second Vendor – Public Key Authentication optimization
Second Vendor – Public Key Authentication optimization in Version v2020.6.27.0
As mentioned in a previous blog post we’ve added a second SFTP vendor in LimagitoX File Mover
Vendor 2 is also able to logon using Public Key Authentication. To achieve this, the SFTP Client (our File Mover in this case) needs to add your Private Key (and Private Key Password).
Quite some types of private key files can be used. It is important to use the correct file extension.
We are also able to use private keys within certificate file types like:
.cer, .crt, .p7b, or .pem
.p12 or .pfx (PKCS #12)
Note: If the PFX contains multiple certificates, the 1st certificate in the PFX is loaded.
A private key file with .ppk as extention will be threaded as a PuTTy key.
Also the following private key file types are supported:
KCS1, PKCS8, PEM, JWK, PVK, etc.
If you need any help , please let us know.
Best Regards,
Limagito Team
By Limagito-Team SFTP Authentication, Public Key, PuTTy, SFTP
21 Jun
Second SFTP Vendor option was added in LimagitoX File Mover
A second SFTP vendor was added in LimagitoX File Mover version v2020.6.21.0. This second SFTP vendor is also based in the USA and has a long history with providing API’s for many internet protocols. The reason we did this is because there are quite some different SFTP servers out there and it seems we couldn’t cover them all. With a second vendor we try to minimize this.
Switching can be done on the fly. Default is still the original vendor (Vendor 1 – SB) which we are using for quite some time now. This new option is available under the ‘Common’ tab of your SFTP setup. Feedback experience about using the new vendor would be much appreciated.
With our second vendor (Vendor 2 – CK) we are able to get more debug information in case of problems. You’ll need to enable ‘Add Control Information to log’ to achieve this.
The following SSH connection protocol algorithms are supported:
Hostkey Types: ssh-rsa, ssh-dsa, ecdsa-sha2-nistp256, rsa-sha2-256, rsa-sha2-512, ssh-ed25519
Key Exchange Methods: curve25519-sha256@libssh.org, ecdh-sha2-nistp256, ecdh-sha2-nistp384, ecdh-sha2-nistp521, diffie-hellman-group-exchange-sha256, diffie-hellman-group-exchange-sha1, diffie-hellman-group14-sha1, diffie-hellman-group1-sha1
Ciphers: chacha20-poly1305@openssh.com, aes256-ctr, aes192-ctr, aes128-ctr, aes256-cbc, aes192-cbc, aes128-cbc, twofish256-cbc, twofish128-cbc, blowfish-cbc, 3des-cbc, arcfour128, arcfour256
MAC Algorithms: hmac-sha2-256, hmac-sha2-512, hmac-sha1, hmac-md5, hmac-ripemd160, hmac-sha1-96
Compression: none, zlib, zlib@openssh.com
…
If you need any help , please let us know.
Best Regards,
Limagito Team
By Limagito-Team SFTP Chilkat, SFTP, vendor
11 Apr
How-To use an X.509 Certificate for SFTP Public Key Authentication
In version v2020.4.11.0 we added X.509 Certificate support for SFTP Public Key Authentication.
Some FAQ:
SFTP authentication using private keys is generally known as SFTP Public Key Authentication. So we need a private key file in the SFTP Setup.
As default we first try to load the RSA/DSA private key from the file.
If this doesn’t work we’ll try to import the file as X.509 Certificate.
Authentication with an X.509 certificate is possible in two modes:
Full: The certificate is sent to the server. This assumes the server can handle certificate authentication. Set ‘Cert Auth Mode’ to ‘Auto’ (= default).
Key-Only: Only the keypair is used. This works with servers that don’t support certificates. Set ‘Cert Auth Mode’ to ‘Raw Public Key’.
If you need any help, please let us know.
Regards,
Limagito Team
By Limagito-Team SFTP SFTP, X.509

← 1 2 3 4 →

Contact Us Now

SFTP

Second Vendor – Public Key Authentication optimization

Second SFTP Vendor option was added in LimagitoX File Mover

How-To use an X.509 Certificate for SFTP Public Key Authentication

SEARCH

CATEGORIES

ARCHIVES

TAGS

DISCOVER OUR SITE