Default URL handler works for ssh1 and ssh2 url's, not for ssh

[renep]

I'm managing Linux VPS's in a cloud, and the web interface of the cloud provider has a convenient button tot open an ssh session to a VPS using a link like:

ssh://user@111.222.111.222/

I would like that button to launch SecureCRT.

In the Global options of SecureCRT, category Terminal > Web Browser, I found these two buttons:

1. SSH2: Make SecureCRT your default SSH2 application
2. SSH1: Make SecureCRT your default SSH1 application

These buttons work fine for ssh1: and ssh2: url's.

Unfortunately, a plain ssh url without the protocol version number doesn't work. Why is there no button for ssh?

How do I manually create an association with the ssh protocol? What are the registry keys I need to create/edit?

I'm using SecureCRT 7.2.4 on Windows 7.

[rtb]

Hi René,

There is a button for SSH1 and SSH2 since those are the protocols. There is no SSH protocol.

I ran a test creating my own registry key, and it did work. Here is an export of the registry key I created:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\ssh]
"URL Protocol"=""

[HKEY_CLASSES_ROOT\ssh\shell]

[HKEY_CLASSES_ROOT\ssh\shell\open]

[HKEY_CLASSES_ROOT\ssh\shell\open\command]
@="\"C:\\Program Files\\VanDyke Software\\SecureCRT\\SecureCRT.exe\" %1"

Does this work for you?

[renep]

Originally Posted by rtb

There is a button for SSH1 and SSH2 since those are the protocols. There is no SSH protocol.

If I'm not mistaken, the "ssh" in the URI is a scheme. The schemes are registered by IANA as per RFC 3986 and
RFC 4395. The IANA URI scheme registry currently contains 'ssh' and not 'ssh1' or 'ssh2'.

So according to these Internet standards, SecureCRT supports two unregistered URI schemes for SSH, but not the registered scheme. IMO that's a bug.

Here is an export of the registry key I created:

Okay, that works. Thank you.

For other people who may be reading this in the archive, on my system the location of SecureCRT in the open command is:

"C:\Program Files\VanDyke Software\Clients\SecureCRT.exe" %1

[rtb]

Thanks for the feedback René.

I have created a bug report on your behalf. We will post here with any updates.

If you would like to be notified directly, please complete and submit the form at the following location:

Submit Bug Report

[renep]

Okay, thank you.

It's nice magic by the way, to click on a VPS in a web control panel and instantly get a root prompt in SecureCRT using public key authentication.

Many installation programs on Windows offer to make their software the default handler for certain URI schemes or file extensions. I'd expect the SecureCRT installer to do this for the ssh scheme, and the SecureFX installer for sftp.

[rtb]

Hi René,

I have created a feature request to add the ability to set SecureFX as the default SFTP handler as well. We will post to this thread if we add the feature in the future.

If you would like to be notified directly, please complete and submit the form at the following location:

Submit Feature Request

In the meantime, you could use the same concept used for ssh to create a URI/URL handler for sftp. I tested this and it works.

[Maureen]

The ability to set SecrureCRT as the default SSH handler has been added to a pre-beta version of SecureCRT for Windows. This allows links such as:

ssh://user@111.222.111.222/

to launch SecureCRT. If you would be interested in trying it, please send email to me at Maureen.Jett@vandyke.com.

Maureen

[renep]

Originally Posted by Maureen

The ability to set SecrureCRT as the default SSH handler has been added to a pre-beta version of SecureCRT for Windows.

Thanks, that's good news.

If you would be interested in trying it

I'd like to try it in the public beta.

[Maureen]

Originally Posted by renep

Thanks, that's good news.



I'd like to try it in the public beta.

The public beta of SecureCRT 7.5 is expected to be available later this year. The exact date hasn't been determined yet.

Maureen