wodSSHTunnel ActiveX Control - HostFingerprint Method
      
 

Description

Called when the remote server provides public key fingerprint information.


Return Type

None  


Syntax

object.HostFingerprint Owner, Fingerprint, Accept



The HostFingerprint Method syntax has these parts:

Part Description
object An expression evaluating to an object of type wodTunnelNotify.
Owner Required. A wodTunnelCom object. Reference to the wodTunnelCom instance that called this notification method.
Fingerprint Required. A String value. Represents fingerprint information for the server.
Accept Required. A Boolean value. When set to False, wodSSHTunnel aborts the connection.

Remarks

This method is called only if you have implemented the IwodSSHTunnelNotify interface in your application and the wodTunnel1.Notification property has received a reference to an instance of your implementation.

Because the SSH architecture does not know about certificates or other means of checking if a remote server is really the one you intended to connect to, the decision to accept a connection or not is a matter of trust.

This is how SSH works in real life - once you connect to the remote server and you are sure it is really the server you expect it to be, you should store the Fingerprint information locally. For each new connection, you should test that the Fingerprint information is the same as the stored value to be sure that no one is 'in the middle' spying on your connection. Fingerprint information is almost unique among servers and it is generated from a server's private key.

If you set Accept to True (default), wodSSHTunnel will continue to perform negotiation with the server normally. If you set it to False (for example, because you see that the Fingerprint information is not the same as last time you connected to this server), it will drop the connection.

Even if you connect to the same server, different protocol versions will produce different Fingerprint information. For example, SSH1 provides different FingerPrint information than the SSH2 service running on same computer and on same port.