v9.5.0.40 Micro Update: New Chilkat Classes/Objects: CertChain, XmlCertVault, Pfx

This new version includes the following updates/fixes: Fix relating to DSA signature verification internal to PKCS7. SFTP: The PreserveDate property now affects both uploads and downloads. Starting in v9.5.0.40, the UploadFileByName method will preserve the last-mod date/time for the file that is uploaded. Note: The SyncTreeUpload/Download methods already preserve the last-mod date/times regardless of the PreserveDate property setting. Fixed SendEmail […]

v9.5.0.38 Micro Update: TrustedRoots Object/Class Added, and other various fixes

This new version includes the following updates/fixes: Added the TrustedRoots class to allow for programss to globally specify a specific set of trusted root CA certificates for PKCS7 certificate signature verification and for SSL/TLS server certificate trust. Added the RequireSslCertVerify property to Http, IMAP, Socket, and MHT. Added the CrcFile and CrcBytes methods to the Crypt2 API. Added a new […]

v9.5.0.37 Micro Update: Mime.LoadMimeBytes Updated to Handle Mixture of bare-LF and CRLF Line Endingss

It was found that in some cases, OpenSSL may produce MIME with a mixture of both bare-LF line-endings and CRLF line-endings. MIME documents *should* always use CRLF line endings. The mixing of both line-ending types in a single MIME document caused the LoadMimeBytes method to skip past the end of the top-level header (terminated by a double bare-LF) and instead […]

v9.5.0.34 Micro Update: SSL/TLS Perfect Forward Secrecy, Minor HTTP and ASN.1 Fixes

The internal Chilkat SSL/TLS implementation now supports the TLS_DHE_RSA_WITH_AES_256_CBC_SHA and TLS_DHE_RSA_WITH_AES_128_CBC_SHA cipher suites. These allow for perfect forward secrecy. Note: This is implemented on the client-side for all protocols using SSL/TLS. The SSL/TLS client provides the server with a list of algorithms it supports, and it is the server that decides which is to be used. These new algorithms are […]

v9.5.0.32 Micro Update: HTTP Connection Left in Invalid State after Event Callback Aborts Operation

For HTTP requests that have KeepAlive indicated in the response header, the internal connection is not closed so that a subsequent request may continue using the existing connection. However, when the client application aborts in the middle of receiving the response, the connection must be closed to avoid being left in an invalid state (where the some of the remainder […]