Send us a question or comment
   

When I connect to VShell® 2.0.1 with an OpenSSH client I get the following error: sigbloblen 55 != SIGBLOB_LEN

This error message is due to OpenSSH, PuTTY and other clients misparsing the version information that VShell is sending. As a result, these clients are incorrectly enabling a compatibility mode.

The solution is to disable sending version information to a client when it connects to VShell. This is documented in the VShell Help file. First, make sure that the VShell control panel is not running, and make the following change to your server configuration:

By default, VShell identities itself to clients by adding product and version information to the protocol version string sent when a connection is made. If you do not want to reveal this information, you must set the following Windows NT registry entry to 0:

HKEY_LOCAL_MACHINE\Software\VanDyke\VShell\Server\Reveal Version Info

When this entry is set to 0, VShell will report "SSH-2.0-0.0" as its version string to connecting clients.

Note: Some clients may not behave correctly when this entry is set to 0.

Was this information helpful?
Yes No
Thank you!
Send your comments and questions to VanDyke Software Support,
or join the discussion in the VanDyke Software Forums.
Can't find the answer you're looking for?
Ask VanDyke Software Support directly
and we will get back to you as soon as possible.
Three Fast Ways to Learn More About VShell for Windows and UNIX
Tell me more. E-mail us your questions about putting VShell to work for your organization.
Try it today! Download a free 30-day evaluation copy of VShell for Windows or UNIX.
Talk to us. Let us help define the right VShell server solution for your company.