ECDSA support on SecureCRT iOS?

[JaTu]

I'm trying to import the EC-key for my servers into SecureCRT iOS, but all I'm getting is a forever loop for passphrase? Something here makes me think, that EC is not supported at all and that's the app's way of telling me that.

Any truth to that? Is EC supported in iOS or not?

Regards,
Jari Turkia

[bgagnon]

Hi JaTu,

I am seeking verification, but I believe that is the case.

I have added this thread to a feature request in our product enhancement database for support of ECDSA keys in SecureCRT/iOS. Should a future release of SecureCRT include this feature, notification will be posted here.

If you prefer direct email notification, send an email to support@vandyke.com and include "Feature Request - Forum Thread #12903" in the subject line or use this form from the support page of our website.

[bgagnon]

Hi JaTu,

It is believed this now works in SecureCRT for iOS 2.1, which was released in the App Store about a week ago.

[JaTu]

It is believed this now works in SecureCRT for iOS 2.1, which was released in the App Store about a week ago.

Nope. Still asking for private key passphrase in a forever-loop.

The private key is your regular OpenSSH-generated ECDSA 521-bit. Headers:

-----BEGIN EC PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: AES-128-CBC,

[bgagnon]

Hi JaTu,

I have submitted this behavior for investigation by the development team. Should progress be made toward a resolution, or further information be requested, I will post in this thread.

If you prefer direct e-mail notification, contact support@vandyke.com and include "Bug Report - Forum Thread #12903" in the subject line.

[bgagnon]

Hi Jatu,

We are not able to reproduce this issue. We'll need to get some info from you, some of which may be sensitive so please send an email to support@vandyke.com and include "Attn Brenda - Forum Thread #12903" in the subject line.

If you can attach Trace Options output of the failed connection to the email, that'll be a great start.

To enable trace options output:

• First, open SecureCRT's main File pull-down menu and select Trace Options. If you open the File pull down menu again you should see a checkmark next to Trace Options, indicating that troubleshooting output is now enabled.
  
• Next, connect to the remote machine. With trace options enabled, you will notice debugging information displayed in the terminal window that isn't normally there by default when SecureCRT is attempting to establish a connection, and at certain times throughout the lifetime of the connection.
  
• Once the problem occurs, please right-click inside the terminal window and choose Select All, then right-click again and choose Copy to transfer the information to the clipboard.
  
• Finally, open a text editor, paste the information from the clipboard into the editor program, and save it as a text file.

NOTICE: The requested troubleshooting data may include sensitive information (usernames, passwords, publicly-accessible host names or IP addresses, etc.).

Please redact sensitive information that would not be appropriate for email communication prior to sending the requested information.

If there is sensitive information that must be conveyed in order to provide a complete picture of the scenario you're facing, please let us know and we will set up a secure upload mechanism that can be used.