COM-based programmatic configuration
Bitvise SSH Server comes with a COM DLL which can be used to configure SSH server settings programmatically from within a Visual Basic script or any other programming language that provides access to COM objects (.NET). Example scripts (renamed to .txt from original .vbs extension):
- Load, Update and Apply Settings
- Export Public Key in OpenSSH known_hosts Format
- Loops through Windows account entries, resetting their mount points so that each account has a single mount point with a real root path set to the value of the "Initial terminal shell directory" for the account
The configuration COM object can be used for the same purposes as the BssCfg utility and the Bitvise SSH Server Control Panel: keypair management, import and export of settings, changing and inspection of individual settings values.
A list of the COM object's supported methods can be found in the SSH server's installation directory in the file BssCfgManip.idl.
BssCfgManip COM object name
The exact name of the BssCfgManip COM object is changed in SSH server versions that contain changes to the configuration format. To find the name of the COM object for your installation, check the file BssCfgManip.idl in the Bitvise SSH Server installation directory.
For example, if your SSH server version is 6.02, the name of the object would be "BssCfg601.BssCfg601". This is because, even though your version is 6.02, the configuration format was last changed in version 6.01.
Virtual filesystem providers
Bitvise SSH Server supports pluggable filesystem providers. Third parties can implement custom providers to support any type of backing store for files accessed with SFTP or SCP via an SSH session. Possibilities include SFTP/SCP access to files contained in an encrypted database; or a bridge that permits SFTP/SCP access to files actually hosted on an FTP server. Third-party providers can be mounted concurrently with the SSH server's default provider, FlowSfsWin, allowing SSH users to access the Windows filesystem and a third-party provider's virtual filesystem concurrently.
Virtual filesystem providers need to be implemented as 32-bit DLLs with a plain C interface. No licensing or royalty fees are required. Feel free to contact us to receive the header files needed.