Posted:  07 Nov 2008 06:53
	Registered User Currently Offline	Posts:  8 Join Date: Nov 2008
How do i make the Sysax Ftp client work with SSH.com's Tectia SFTP server? Trying to use PuTTy key gen and export to OpenSSH format. Some how it fails. Any help is appreciated

Posted:  07 Nov 2008 06:55
	Moderator Currently Offline	Posts:  367 Join Date: Nov 2008
Are you having problems logging on to the server with a username and password or are you having a problem only when using public key authentication? Also, what version of Tectia is the remote computer running?

Posted:  07 Nov 2008 06:57
	Registered User Currently Offline	Posts:  8 Join Date: Nov 2008
I am using public key authentication. The sever version should be 5.3. Are you having problems logging on to the server with a username and password or are you having a problem only when using public key authentication? Also, what version of Tectia is the remote computer running?

Posted:  07 Nov 2008 06:59
	Moderator Currently Offline	Posts:  367 Join Date: Nov 2008
The issue may also be with the Tectia server. The server may require the public key to be in a specific format. You can verify if the pkeyload command in sysax ftp automation is working by trying to setup public key autthentication on Sysax Multiserver.

Posted:  07 Nov 2008 07:01
	Registered User Currently Offline	Posts:  8 Join Date: Nov 2008
Yes, the issue could be with Tectia server. How could i make the public key in specific format? The requirement for Sysax FTP client is, the private key should be of OpenSSH format. Other key format will not work. Any specific procedure to be followed... I have tried this: - used PuttyGen to generate new public & private key. - used the export option to save the key in OpenSSH format. - used the key generated in step 2 in the ftp script (in pkeyload function) - uploaded the PUBlic key to the Tectia server's authrorized_keys file. The issue may also be with the Tectia server. The server may require the public key to be in a specific format. You can verify if the pkeyload command in sysax ftp automation is working by trying to setup public key autthentication on Sysax Multiserver.

Posted:  07 Nov 2008 07:02
	Moderator Currently Offline	Posts:  367 Join Date: Nov 2008
Do you know what solution Tectia recommends to setup public key authentication for their server? Once you have this information, we can see if the private key can be converted to a pem format.

Posted:  07 Nov 2008 07:05
	Registered User Currently Offline	Posts:  8 Join Date: Nov 2008
I have downloaded the trial edition of Tectia and trying it out. Btw, we are using Sysas FTP automation to connect to another vendor's site to upload our data. Since the troubleshooting @ the vendor side is troublesome, i am trying to identify what could be the reason. My colleague, generated the public and private keys using PuTTyGen and psftp to connect to the server successfully. But when i tried to use the same key and export to OpenSSH format, it does not work with Sysax FTP. Do you know what solution Tectia recommends to setup public key authentication for their server? Once you have this information, we can see if the private key can be converted to a pem format.

Posted:  07 Nov 2008 07:08
	Moderator Currently Offline	Posts:  367 Join Date: Nov 2008
Ok. I am assuming that you only converted the private key to openssh format. Does the unconverted key work successfully with psftp for you?

Posted:  07 Nov 2008 07:10
	Registered User Currently Offline	Posts:  8 Join Date: Nov 2008
Yes, it worked, as my colleague tested. I am assuming that you only converted the private key to openssh format. Does the unconverted key work successfully with psftp for you?

Posted:  07 Nov 2008 07:12
	Moderator Currently Offline	Posts:  367 Join Date: Nov 2008
so it looks like we have isolated the issue to the conversion process. Can you explain the exact steps you used to convert the private key that you got from puttygen to pem format. This will help our developers to try the same procedure and debug the issue.  Or it could be, I am missing some steps in my Tectia server setup. Here is what I did... - Generate the public and private key using PuttyGen - Use the Convesions-> Export OpenSSH Key to get the PEM fi so it looks like we have isolated the issue to the conversion process. Can you explain the exact steps you used to convert the private key that you got from puttygen to pem format. This will help our developers to try the same procedure and debug the issue.

Posted:  07 Nov 2008 07:15
	Registered User Currently Offline	Posts:  8 Join Date: Nov 2008
Attachment: tectiaDebugLog.txt; size=0; (0 kb); mylog.log; size=0; (0 kb)  I have done the following... - created the keys using the Tectia server, using "ssh-keygen2", defa= ult options, DSA key pair. - imported the private key in PuTTy Gen and used : Conversions -> Export as OpenSSH key - Updated the PUBLIC key in the Tectia server - Tried connecting to the server using the SysaxFTP Now, I think all the authentication are fine, but still some error messages... The following is the error from Sysax ftp automation script... [ERR] An bogus channel packet was received [ ] Script Engine: Line 67: Executing waitsecs. Parameter(s): 10 [ ] Script Engine: Script execution stopped due to a limit of 15 commands Your help is highly appreciated!

Posted:  07 Nov 2008 07:17
	Moderator Currently Offline	Posts:  367 Join Date: Nov 2008
Could you create a new pair of keys using Tectia and send it to us? We can try to duplicate the condition here for debugging.

Posted:  07 Nov 2008 07:25   Last Edited By: sysaxsupport
	Registered User Currently Offline	Posts:  8 Join Date: Nov 2008
Attachment: id_dsa_2048_b.pub; size=0; (0 kb); id_dsa_2048_b; size=0; (0 kb)  If you have Tectia server at your end, you can generate on your own. Attached is the keys generated using Tectia. BTW, why there is no details of full conversations in these email exchanges?

Posted:  07 Nov 2008 07:31   Last Edited By: sysaxsupport
	Registered User Currently Offline	Posts:  8 Join Date: Nov 2008
I managed to solve the issue. You can close the case... Used ssh.com's ssh-keygen2 to create the keys and converted using PuttyGen. Upon proper configuration @ the SSH Tectia server, it started to work.

Copyright © 2021 Codeorigin, LLC - All Rights Reserved.
RSS 2.0 Atom 1.0