ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When Terramate executes commands that contact a remote backend or Terramate Cloud endpoint presenting a self‑signed or privately issued TLS certificate, the connection aborts with an x509: certificate signed by unknown authority error. The only way to make the TLS handshake succeed is to add the certificate authority to the operating system's trust store or
Suppose I am at network where there is MITM SSL swaping firewall (google.com is not issued by Google, but reissued by custom CA root authority) some more details here https://security.stackexchange.com/questions/107542/is-it-common-practice-for-companies-to-mitm-https-traffic . I have simple Dockerfile: FROM alpine:latest RUN apk --no-cache add curl It fails
Problem Context Sulu relies on Symfony’s HttpClient, wrapped by the Elastica library, to talk to Elasticsearch. When the Elasticsearch endpoint is HTTPS and presents a self‑signed or otherwise untrusted certificate, the client throws a TransportExceptionInterface with the message SSL certificate problem: unable to get local issuer certificate . Configuration
When adding a custom domain to Railway, the platform automatically provisions a managed TLS certificate using Let's Encrypt. The goal is to guarantee that the certificate is issued and renewed successfully even when the domain's DNS TTL is set higher than Railway's 60‑day renewal interval. However, Railway's internal DNS resolver caches responses for up to f
Harbor LDAP over TLS: Supplying Custom CA Certificates The goal is to allow Harbor’s LDAP authentication module to trust a self‑signed or internal CA‑signed LDAP server certificate without altering the host’s global trust store or disabling verification. Current Harbor releases (2.0‑2.12) rely on the Go LDAP library’s default certificate pool, and the extern
When an application uses SQLAlchemy to connect to a PostgreSQL database via psycopg2, the sslmode parameter controls TLS certificate validation. Setting sslmode='verify-full' should cause the driver to reject connections whose server certificate cannot be verified against the supplied CA bundle. The goal is to determine how SQLAlchemy propagates any SSL erro
Ballerina Network Behavior The goal is to confirm how the Ballerina runtime handles certificate validation during external network operations. Constraints The uncertainty lies in whether the language provides fine-grained control over TLS validation parameters, or if it relies entirely on the underlying environment's defaults. What specific runtime mechanism
commented · 26 Jun 2021, 14:32 UTC
docker
elasticsearch
railway
harbor
sqlalchemy
ballerina