Devart SecureBridge v9.0.2 Professional D7-XE-Berlin-Tokyo-Rio
Devart SecureBridge v9.0.2 Professional D7-XE-Berlin-Tokyo-Rio
SecureBridge represents clients and servers for SSH, SFTP and SSL protocols as a network security solution. It protects any TCP traffic using SSH or SSL secure transport layer protocols, that provide authentication for both client and server, strong data encryption, and data integrity verification. SecureBridge components can be used in conjunction with data access components to prevent data interception or modification in an untrusted network.
Our security solution is very convenient in setup and usage. It is enough to place several components on the form and specify the server address and the user login information to establish a secure connection. Applications that have to work with secure information are easy to deploy, as they do not require any external files.
Data Protection and Encryption Solutions
SecureBridge protects transferred data against different kinds of attacks. SecureBridge uses the Diffie-Hellman key exchange algorithm for secure network connection establishing. A reliable random number generator is used for generating keys. To protect data against illegal access, information gets encrypted by symmetric algorithms that provide high speed and reliability. For data integrity verification hash algorithms like SHA1 are used.
Cross-Platform Solution for Delphi and C++Builder
This high-performance and feature-rich library of components combines cross-platform solutions for developing applications using various IDEs and editions including Community Edition: RAD Studio, Delphi, C++Builder, Lazarus (FPC) on Windows (for both x86 and x64 platforms), macOS, iOS, Android, Linux and FreeBSD.
Support for Third-Party Components
SecureBridge supports Internet Direct components (Indy) and Data Access Components for MySQL and PostgreSQL (MyDAC, PgDAC, UniDAC) . This allows you to implement all the advantages of encrypted connections within a single application without any external files.
Full Support for SSH2 Protocol
SecureBridge supports SSH2 protocol which is one of the most reliable protocols for data encryption. SSH2 is an acknowledged industry standard in the area of secure data transfer through unprotected connections.
SSH Server
High-performance SSH server with wide abilities for connection setup and users management. SSH server works with different types of SSH clients such as OpenSSH, PuTTY etc. Number of the clients connected simultaneously is limited only by system resources.
SSH Client
Use the TScSSHClient component, that represents SecureBridge SSH client, to work with different SSH servers like OpenSSH, WinSSHD. It allows you to achieve high performance due to connection parameters management. SSH client unites several unprotected channels from client to server in one protected connection. Logical channels can exist in different threads.
SFTP Client
Transfer files and access file system securely using the SecureBridge SFTP Client, that is implemented in the TScSFTPClient component.
Full Support for SSL 3.0 and TLS 1.0, 1.1 & 1.2 Protocols
Our components support Secure Socket Layer (SSL) protocol, which is one of the most reliable protocols for data encryption along with SSH. SSL is a widely used protocol for ensuring safety of financial operations in Internet. Any Internet-resource that deals with money, protects its operations with SSL.
SFTP Server
In addition to the possibility of using an SFTP client for secure file downloading, you now get a great functionality to create your own SFTP server using the TScSFTPServer component.
SSL Client
SecureBridge SSL client is implemented in the TScSSLClient component. It can work with other applications through SSL 3.0 and TLS 1.0 protocols. SSL client validates server certificate, encrypts/decrypts data transferred through a network.
How Does SecureBridge Work?
In order to ensure data safety in insecure networks, it is essential to take care of data protection and integrity, as well as of data receiver identification. So before putting the data into the insecure area, it should be encrypted. On the other side the data should be decrypted. In a general case an encrypted connection between a client and a server may look like this:
Both security client and security server can be implemented with SecureBridge just by adding several components into your application. This will not affect its architecture, and will not add any external dependencies. It is also possible with SecureBridge to make separate security client and server applications to protect connections between trusted networks.
Both SSH and SSL are designed to protect network connections. As these protocols have certain differences, they have to be described separately.
SSH tunnel can ensure data transferring from several clients of one secure area to clients in another secure area through one protected TCP connection.
SecureBridge can act as both SSH client (TScSSHClient) and SSH server (TScSSHServer). In some cases SSH client and SSH server are embedded into applications whose connections have to be protected.
SSL connection resembles SSH tunnel. The difference is that SSL client and SSL server are always embedded into applications. To put some data into network, an application calls methods of the embedded SSL client/server, and data is encrypted and sent. To get data from network, the application also calls methods of SSL. So, SSL clients and servers operate within the application's address space. The general chart of computer ties when connecting through SSL is presented below:
9.0.2 21-Feb-19
Support for login to FTP server as Anonymous is added
Bug with using ECDSA host key in SSH protocol is fixed
Bug with validation of certificate with wrong identity DNS name is fixed
Bug in TScSFTPServer.GetFullPath method for Linux is fixed
Bug with SSH channel threads termination is fixed
Support for login to FTP server as Anonymous is added
Bug with using ECDSA host key in SSH protocol is fixed
Bug with validation of certificate with wrong identity DNS name is fixed
Bug in TScSFTPServer.GetFullPath method for Linux is fixed
Bug with SSH channel threads termination is fixed
Only for V.I.P
Warning! You are not allowed to view this text.