security admin - SocketTools Library Edition

Release Notes: This was related to a change made in the previous release that removed deprecated security functionality. 0 ...

Release Notes: to fail on systems that do not have IPv6 enabled. Corrected an issue which could prevent secure TELNET connections from being negotiated using TLS. Corrected an issue which could result in a memory leak ... security related functionality implemented for Windows Vista, which is no longer a supported platform. Removed legacy support for deprecated cipher suite components using TLS and SSH for secure connections. ...

Release Notes: documentation. Corrected a critical issue with secure connections which could cause the TLS stream buffers to be corrupted if the buffer size exceeded 16KiB. Corrected an issue which could result in an incomplete ...

Release Notes: Added support for the HTTP/2.0 protocol in all HTTP client components. Updated security options for TLS 1.2 (and later versions) and SSH 2.0 to use cipher suites available in Microsoft Windows 11 ... and Windows Server 2022. Older, less secure cipher suites have been deprecated and will not be used when establishing a connection. A fallback option is available to connect to legacy servers using TLS 1.0. ... The default security protocol and cipher suite selection for all secure connections have been updated for Windows 10. Expanded support for internationalization and Unicode for all components. This also extends ...

Release Notes: names. Corrected an issue which could result in a rare deadlock condition when creating simultaneous secure client connections. Corrected an issue which could cause memory corruption when attempting ...

Description: interface provides both synchronous and asynchronous network connections. Secure connections are supported using the Secure Sockets Layer (SSL), Transport Layer Security (TLS) and Secure Shell (SSH) ... protocols. Security features in the components can be enabled with just a few lines of code and do not require any experience with data encryption or cryptography. The SocketTools libraries are native Windows ...

Release Notes: securely to certain legacy servers which still use TLS 1.0. Corrected an issue which could cause an unhandled exception in the MIME and Encoding components when decoding a string which contains certain ...

Release Notes: when a secure connection is established. This only affected services which required TLS client certificates for user authentication. ...

Release Notes: switch to using a secure port (443) instead of returning an error. The HTTP server components and libraries will no longer override custom values for the Cache-Control, Content-Type and Server response ...

Release Notes: Secure connections will now automatically fall back to using TLS 1.2 if support for TLS 1.3 has not been enabled on the local system. Microsoft has not made TLS 1.3 generally available ...

Release Notes: over a secure connection. Corrected an issue with the NNTP client components and library which could cause very large article IDs to be truncated to 32-bit values and then returned as negative integers ...

Release Notes: prevent a secure HTTP session from being established with a server that used TLS 1.0 and required a client certificate. Note that TLS 1.0 is considered a deprecated version of the protocol, and by default ... code for the current thread would not be updated correctly under certain conditions when a secure connection could not be established with the server. Corrected an issue with the SMTP and Text Messaging ...

Release Notes: Improves support for 8-bit character sets for Japanese, Korean, Chinese, Arabic, Hebrew and Russian. Added support for TLS session reuse for secure FTP connections. This option should only be used ...

Release Notes: Updates compression and security related libraries used internally to address potential buffer overflow problems. Modified the MIME components and API to manage memory more efficiently when ... as the preferred encryption method. Modified the fallback option to use earlier versions of TLS with legacy servers so it always includes TLS 1.0 as a supported option regardless of the selected security protocol ... version, and will always permit the use of older cipher suites. By default, SocketTools will only use TLS 1.2 and strong cipher suites for secure connections. Updated several compression and security related ...

Release Notes: to security and performance. ...

Release Notes: any location. The data is stored securely, and all connections to the server use TLS 1.2 and AES 256-bit encryption. Because there are no public endpoints to the data that you store, it’s not possible ...

Release Notes: and will reset security options to their default values. The base domain name for a host will be queried when resolving DNS mail exchange (MX) records if the specified host name does not have any records defined. ... Additional checks are made to ensure the validity of certificates that are used to accept or establish secure connections. Corrected a problem in the FTP and HTTP components and libraries where the GetFile ... aborted a secure connection during the TLS handshake. Corrected an issue where the FTP client components could generate too many progress event notifications over a short period of time during large file ...

Release Notes: Updated security related internals to prioritize stronger encryption and hashing algorithms, Secure connections using SSH will no longer support the v1 protocol by default when establishing ... the connection because SHA-1 is a weaker hash algorithm. All SocketTools components and libraries will now use TLS 1.2 as the default for secure connections and will not advertise support for earlier, less secure ... versions of the TLS protocol be used if required. Updated security related internals to prioritize stronger encryption and hashing algorithms in conjunction with the change to use only TLS 1.2 as the default ...

Release Notes: Updates in V7.0 Now includes both 32-bit and 64-bit components Supports IPv4 and IPv6 network connections Includes all of the security features that were previously only available in the Secure ...

Release Notes: Adds support for Windows 10 and Windows Server 2016. Support for Windows 10 and Windows Server 2016 platforms and the current version of the TCP/IP stack on those platforms. New security options ...