SocketTools Library Edition 9.2

Se han actualizado los elementos internos relacionados con seguridad para dar prioridad a un cifrado más fuerte y a algoritmos de hashing.
Noviembre 7, 2017
Nueva versión

Características

  • Secure connections using SSH will no longer support the v1 protocol by default when establishing a connection. This version of the protocol is considered deprecated and will only be used if the application explicitly requests it. By default, all SSH connections (including connections to SFTP servers) will use SSH v2.
  • The internal list of various cipher suites offered by the SSH components has been modified to prioritize SHA-256 over SHA-1. This addresses a problem where some SSH servers would reject 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 protocol. If the platform is Windows XP, Windows Vista or Windows Server 2003, then TLS 1.0 will be supported for backwards compatibility. Applications may still explicitly request that older 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 protocol. When connecting to older servers that have not been updated to use more recent cipher suites, it may be necessary to explicitly specify that the control or library use TLS 1.0 in addition to or instead of TLS 1.2.
  • TLS Session Resumption is available on Windows 8 and later versions of the platform for client-side connections. Server support is available on Windows 8.1, Windows 10 and Windows Server 2016. This feature is not available on earlier versions of Windows.
  • The FtpServer and HttpServer ActiveX controls and .NET classes will now validate the server certificate before allowing the server to start. Previously, the certificate validation was done at the point where a client would connect to the server. With this change, the server application will immediately know if the certificate does not exist or is invalid.
  • The OnProgress event for the FtpClient and HttpClient ActiveX controls will now return the number of bytes copied and the total number of bytes as a Double floating-point number if the value would exceed 2 GiB, the maximum value that can be represented as a signed 32-bit integer.
  • The TransferBytes property for the FtpClient and HttpClient ActiveX controls will return -1 if the value would exceed 2 GiB, instead of returning an arbitrarily large negative value. If large files are being transferred, the application should use the new TransferBytesXL property which will return the number of bytes as a Double floating-point value.
  • The OnProgress event for the FtpClient and HttpClient .NET class will now return the number of bytes copied and the total number of bytes as a long (64-bit) integer. The TransferBytes property has also been updated to return a long integer value.
  • The HttpClient ActiveX control and .NET class provides improved support for submitting JSON data using the PostJson method. The client library also includes a HttpPostJson function and PostJson method for the C++ class.
  • The TransferBytes, TransferRate and TransferTime properties were added to the HttpClient ActiveX control and .NET class.
  • The TransferBytes, TransferRate and TransferTime property values will now persist after a connection has been closed. Their values will reset to zero when a new connection is established.
  • The FtpClient ActiveX control, .NET class and library will now recognize URIs that use the “ftp-authssl” scheme in addition to “ftpes”
  • Updated the core tracelog (logging) facility shared by all libraries and components to be more efficient when writing large amounts of data, or appending to a large logfile. This should result in a reduced impact on applications where logging is enabled.
  • The default logging mode now includes generating a hexdump of the data exchanged between the client and server. For the ActiveX controls and .NET classes, this typically means that it is no longer necessary to explicitly set the TraceFlags property when enabling logging.
  • Log file names may now contain embedded environment variables that are replaced with their values. For example, a log file name of “%LocalAppData%\MyLogFile.txt” would create the file in the local application data folder for the current user.
  • Log files will be created in the current user’s Documents folder by default, if no folder path is specified. In addition, logging will automatically be disabled if the specified log file is read-only, or if it specifies an executable or system file.

Correcciones

  • Corrected a potential deadlock issue where a background worker thread that established an SFTP connection would connect to a server and then block indefinitely waiting for file transfers to complete on another thread.
  • Corrected several methods in the SocketTools.FileTransfer, SocketTools.FtpClient and SocketTools.HttpClient classes where file offsets were specified as 32-bit integer values instead of 64-bit values, or would truncate 64-bit values to 32-bit values. This would prevent an application from specifying offsets in very large files (over 4.2GiB)
  • Corrected an issue where Unicode file names were not being encoded or decoded correctly in some cases, notably with names that did not contain characters in the Latin-1 character set.
  • Corrected a problem that could result in an unhandled exception when certain malformed URLs would be passed by the caller to the FTP and HTTP components.
  • Corrected a problem where querying a DNS server for a list of mail exchange (MX) records would fail unexpected or return a truncated list of mail servers.
  • Corrected a problem where multiple DNS queries could cause a minor memory leak if the Unicode version of the functions were used.
  • Corrected several methods in various C++ class implementations that did not work correctly or were omitted if the application was compiled using Unicode.
  • Corrected a problem where the TransferRate property could return incorrect values, or no value at all.
  • Corrected a problem where incorrect values could be returned for UTF-8 encoded directory and file names. For example, the GetDirectory method for the FtpClient class could return an invalid value. This was usually indicated by “?” characters being interspersed throughout the string.
  • Corrected a problem where certain valid multipart MIME messages with very large header blocks were not being parsed correctly. Either the message could not be parsed at all, or it would return an incorrect number of message parts, if it included file attachments or alternative message content.
SocketTools Library Edition 9.2
SocketTools Library Edition

SocketTools Library Edition

Bibliotecas de comunicaciones de Internet para C/C++, Delphi y Visual Basic.

Solicitar presupuesto Comprar ahora

SocketTools Library Edition también está disponible en:

¿Alguna pregunta?

Chatee en vivo ahora mismo con nuestros especialistas en licencias de Catalyst Development Corp..