(SQL Server) SSH using SOCKS Proxy

Demonstrates how to connect to an SSH server through a SOCKS4 or SOCKS5 proxy.

Chilkat ActiveX Downloads ActiveX for 32-bit and 64-bit Windows

-- 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)
    -- This example assumes the Chilkat API to have been previously unlocked.
    -- See Global Unlock Sample for sample code.

    DECLARE @ssh int
    -- Use "Chilkat_9_5_0.Ssh" for versions of Chilkat < 10.0.0
    EXEC @hr = sp_OACreate 'Chilkat.Ssh', @ssh OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    -- To use a SOCKS4 or SOCKS5 proxy, simply set the following
    -- properties prior to connecting:
    -- The SOCKS hostname may be a domain name or 
    -- IP address:
    EXEC sp_OASetProperty @ssh, 'SocksHostname', 'www.mysocksproxyserver.com'
    EXEC sp_OASetProperty @ssh, 'SocksPort', 1080
    EXEC sp_OASetProperty @ssh, 'SocksUsername', 'myProxyLogin'
    EXEC sp_OASetProperty @ssh, 'SocksPassword', 'myProxyPassword'

    -- Set the SOCKS version to 4 or 5 based on the version
    -- of the SOCKS proxy server:
    EXEC sp_OASetProperty @ssh, 'SocksVersion', 5

    -- Note: SOCKS4 servers only support usernames without passwords.
    -- SOCKS5 servers support full login/password authentication.

    -- Connect to an SSH server via a SOCKS proxy:
    DECLARE @hostname nvarchar(4000)

    DECLARE @port int

    -- Hostname may be an IP address or hostname:
    SELECT @hostname = '192.168.1.108'
    SELECT @port = 22

    DECLARE @success int
    EXEC sp_OAMethod @ssh, 'Connect', @success OUT, @hostname, @port
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ssh, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ssh
        RETURN
      END

    -- Your application is now connected to an SSH server 
    -- through a SOCKS4 or SOCKS5 proxy. 
    -- ..

    EXEC @hr = sp_OADestroy @ssh


END
GO