✨ New Features Js A new Chilkat class has been added: Js is a minimal, standards-compliant JavaScript engine designed to embed JavaScript inside applications with very small footprint and fast startup. It executes JavaScript code inside an application without requiring a browser or large runtime. See About the Chilkat.Js JavaScript Engine Ai Provider — […]
The main features of this release focus on Chilkat’s Ai class, enabling interactive AI response streaming directly into embedded desktop application browsers. It supports Azure, custom base URLs for OpenAI-compatible providers, and local providers like Ollama. ✨ New Features Ai Real-Time Streaming AI Responses to Embedded Browsers in Desktop Apps — Stream AI responses […]
Previous Version: Chilkat v11.1.0 Release Notes The main addition in v11.2.0 is the Chilkat.Ai class, and the Chilkat.StringBuilder.MarkdownToHtml method. Ai: The Chilkat AI class provides a unified API for interacting with different AI providers: OpenAI, Google, Claude, xAI, Perplexity, and DeepSeek. It provides functionality for conversation management, multimodal inputs, and streaming mode. Markdown to HTML […]
Starting with the v10.0.0 release (end of September 2024), Chilkat moves to standard semantic versioning. Prior to this release, for various technical reasons, Chilkat was stuck with versions 9.5.0.xx, where only xx changed. For this first leap to semantic versioning, where the major version changes to 10 (from 9), there are no backward incompatible changes. […]
The EVOLIUM REDTRUST CSP is not capable of signing a non-hash. In other words, it’s not possible to do TLS 1.2 with client certificates with the RedTrust KSP. This is a common problem in CSP/KSP implementations. They assume that everything to be signed is a hash, such as SHA1, SHA256, SHA384, SHA512, and require the […]
If the problem is with Office365, such as with SendEmail to smtp.office365.com, port 587, then updating to Chilkat v9.5.0.93 or later will solve the problem. For example, if you see the following, then update to v9.5.0.93 or later. … ensureSmtpSession: ensureSmtpConnection: smtpParams: SmtpHost: smtp.office365.com SmtpPort: 587 SmtpUsername: … SmtpSsl: 0 StartTLS: 1 –smtpParams smtpConnect: smtpHostname: […]
Question: We use your system to submit to VAT returns to HMRC using Making Tax Digital. Does this TLS stuff mean anything to you? The only reference I can see to it in the code is setting a TLS Boolean to true, which doesn’t specify a version? (This is a portion of the notice from […]
Question: We are about using Chilkat C++ library for an FTPS connection. I read on online documentation that there is method CkFtp2::put_AuthTls which allows setting TLS connection. Some questions about client behavior according to this method: if we don’t call this method, transmission is in clear text? Is it equivalent to CkFtp2::put_AuthTls(false)? If we call […]
The following error can be caused by firewall restrictions. I do not know the specifics of the firewall restrictions, but the TLS connection completes successfully in the prior call to Chilkat.Rest.Connect(). In other words, the TLS handshake completes successfully and then the firewall closes (or blocks) the connection. ChilkatLog: FullRequestFormUrlEncoded: DllDate: Jul 24 […]
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 […]
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 […]
If this FTP server response is seen in the LastErrorText, it means that the SSL/TLS connection requires a client-side certificate with private key. Prior to connecting, the client-side certificate should be specified by calling the SetSslClientCert, or SetSslClientCertPfx. Make sure to check the return value of these methods for success/failure. If the SetSslClientCert* method fails, […]
Problem: An SSL/TLS connection failed and the LastErrorText contains “SEC_E_INTERNAL_ERROR”, such as in the error text below: (See cause solution below) ChilkatLog: Connect: DllDate: Dec 4 2009 UnlockPrefix: **** Username: **** Component: .NET 2.0 objectId: 1 hostname: *.*.*.* port: 443 ssl: 1 maxWaitMs: 20000 windowsAccount: **** ClientCertDN: **** protocol: default An existing connection was forcibly […]
If you open a DOS prompt and telnet to an SMTP server (typically port 25 for non-SSL, port 465 for SSL), you should get a human-readable printable-text “HELLO” message from the non-SSL port, but binary SSL-handshake protocol gobbly-gook from an implicit SSL port. For example: > telnet mail.chilkatsoft.com 25 220 mail.chilkatsoft.com ESMTP MailEnable Service, Version: […]
