SQL Server

Multi-Hop SSH (SSH Through SSH)

See more SSH Examples

Demonstrates how to SSH through one SSH server to get to another SSH server. The scheme looks like this:

Application => ServerSSH1 => ServerSSH2

The ConnectThroughSsh method is added in Chilkat version 9.5.0.55 to accomplish this task. Technically, it should be possible to chain any number of servers using the ConnectThroughSsh multiple times:

Application => ServerSSH1 => ServerSSH2 ==> ServerSSH3 => ... => ServerSSHN

SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    -- Important: Do not use nvarchar(max).  See the warning about using nvarchar(max).
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    -- This example assumes the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @ssh1 int
    EXEC @hr = sp_OACreate 'Chilkat.Ssh', @ssh1 OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- Hostname may be an IP address or domain name:
    DECLARE @hostname nvarchar(4000)
    SELECT @hostname = '192.168.1.108'
    DECLARE @port nvarchar(4000)
    SELECT @port = 22

    -- Connect directly to the 1st SSH server:
    EXEC sp_OAMethod @ssh1, 'Connect', @success OUT, @hostname, @port
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ssh1, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ssh1
        RETURN
      END

    -- Wait a max of 15 seconds when reading responses..
    EXEC sp_OASetProperty @ssh1, 'IdleTimeoutMs', 15000

    -- Authenticate using login/password:
    EXEC sp_OAMethod @ssh1, 'AuthenticatePw', @success OUT, 'myLogin', 'myPassword'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ssh1, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ssh1
        RETURN
      END

    -- Connect through the 1st SSH connection to reach a 2nd SSH server.
    -- Note: Any number of SSH connections may be simultaneously tunneled through a single
    -- existing SSH connection.
    DECLARE @ssh2 int
    EXEC @hr = sp_OACreate 'Chilkat.Ssh', @ssh2 OUT

    EXEC sp_OAMethod @ssh2, 'ConnectThroughSsh', @success OUT, @ssh1, 'someremoteserver.com', 22
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ssh2, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ssh1
        EXEC @hr = sp_OADestroy @ssh2
        RETURN
      END

    EXEC sp_OASetProperty @ssh2, 'IdleTimeoutMs', 15000

    -- Authenticate with ssh2...
    EXEC sp_OAMethod @ssh2, 'AuthenticatePw', @success OUT, 'myLogin2', 'myPassword2'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ssh2, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ssh1
        EXEC @hr = sp_OADestroy @ssh2
        RETURN
      END

    -- The application may now is connected and authenticated with ssh2.
    -- The application can do whatever it desires just as if it was directly
    -- connected to ssh2.   For example, the application might open
    -- a session channel to send commands or start a remote shell..
    DECLARE @channelNum int
    EXEC sp_OAMethod @ssh2, 'OpenSessionChannel', @channelNum OUT
    IF @channelNum < 0
      BEGIN
        EXEC sp_OAGetProperty @ssh2, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ssh1
        EXEC @hr = sp_OADestroy @ssh2
        RETURN
      END

    -- ...
    -- ...
    -- ...

    -- Close the connection with ssh2.  (This closes the the tunnel through ssh1.)
    -- The connection with ssh1 is still alive, and may be used for more connections.
    EXEC sp_OAMethod @ssh2, 'Disconnect', NULL

    -- ...
    -- ...
    -- ...

    EXEC sp_OAMethod @ssh1, 'Disconnect', NULL

    EXEC @hr = sp_OADestroy @ssh1
    EXEC @hr = sp_OADestroy @ssh2


END
GO