ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
This question concerns Cesanta Mongoose, not the Node.js MongoDB ODM. In mg_tls_opts , the CA bundle ( ca / ca_len ) and expected peer name ( name ) appear to control separate parts of TLS validation: chain-of-trust verification and endpoint identity matching. The unresolved issue is what an application should require when name is unset. Does a successful ha
Goal: Configure the SurrealDB JavaScript client to trust a custom certificate authority while still enforcing hostname verification during TLS handshake. Constraints: The client’s `tls` option accepts a `ca` array for custom CAs and a `rejectUnauthorized` flag that mirrors Node.js TLS settings. Setting `rejectUnauthorized: false` disables all validation, but
Goal Upload coverage reports from CI runners that sit behind a corporate TLS-inspecting proxy, where the Codecov endpoint presents a certificate chained to a private CA. The upload should succeed with full certificate validation intact, not with verification disabled. Constraint From what I can determine, the Codecov uploader (recent versions) validates TLS
FaunaDB’s API endpoints require TLS 1.2+ and present a server certificate signed by a public CA. The official drivers rely on the underlying HTTP library’s default trust store and do not expose a parameter to supply an alternate CA bundle, nor does the dashboard provide a way to upload custom root certificates. This leaves users who operate behind internal P
A Dovecot configuration requires mutual TLS (mTLS) to authenticate clients via certificates. While the ssl = yes and ssl_cert directives are configured for the server identity, the system must also validate the incoming client certificates against a trusted root. The current uncertainty involves the behavior of the ssl_ca directive when managing a complex tr
Goal On CentOS 8, systemd-resolved is active by default and manages /etc/resolv.conf as a symlink to /run/systemd/resolve/stub-resolv.conf , with the stub listener on 127.0.0.53. I need a reliable way to troubleshoot name resolution and TLS certificate validation across tools that may not all consult the same resolver path. Constraints and uncertainty Some u
PyScript currently relies on the browser's fetch API for all module imports, which means DNS resolution and TLS certificate validation are handled entirely by the underlying OS and browser stack. No attribute or environment variable exists to relax these checks, so developers encountering self-signed or expired certificates must resort to server-side fixes o
Context GitKraken validates HTTPS repository connections using the operating system's trusted root certificate store by default. Certain releases also ship a bundled CA certificate bundle, but the conditions under which the client switches to or supplements the system store with this bundle are not documented. Unresolved behavior When the system store contai
Goal Enable a Minitab installation to trust a corporate or self‑signed CA when connecting to Minitab Cloud services. Constraints Minitab relies on the operating‑system resolver and trust store for DNS and TLS. The application offers no UI or command‑line option to import a custom CA bundle, and the current releases do not expose certificate validation settin
mongoose
codecov
dovecot
centos
minitab