ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Security & identity · #openssl
I need to confirm that the version of libssl3 installed on my Debian Bullseye system provides the OpenSSL 3.0.2 features required by a specific application, particularly TLS 1.3 support. The application documentation states that it will fail to negotiate TLS 1.3 if the library is older than OpenSSL 3.0.2, but I am unsure how to check the exact libssl3 versio
Ensure that HTTPS requests made with Ruby's Net::HTTP succeed in production environments where the system may lack a trusted CA certificate bundle. Locally, the default OpenSSL store is usually present, so requests complete without error. In minimal containers or hardened servers, the bundle can be absent, leading to OpenSSL::SSL::SSLError: certificate verif
OpenSSL 3.0 introduced providers as the primary mechanism for loading cryptographic algorithms while retaining the legacy ENGINE API for backward compatibility. The ENGINE interface is marked deprecated, with future releases possibly removing it entirely. Existing hardware acceleration modules written as ENGINEs must be evaluated for migration to the provide
Recovery needs to recreate the working service and its required data after a machine or process is lost. Which artifacts and state need protection, and how should the restore be checked?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
When generating a Certificate Signing Request (CSR) using the openssl req command, standard subject fields are handled via interactive prompts or a basic configuration file. However, modern browser requirements necessitate the inclusion of Subject Alternative Names (SANs) to ensure certificate validity across multiple DNS entries or IP addresses. The goal is
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?
Goal: achieve identical certificate verification results in development and production environments when relying on OpenSSL's default trust store. Constraint: the library's default certificate directory is set at compile time and may differ between machines; if the environment variables SSL_CERT_FILE or SSL_CERT_DIR are defined only in a developer's shell, p
Goal Ensure that OpenSSL’s ASN.1 TIME parsing consistently translates timezone offsets into a predictable representation for applications that convert the returned time to local civil time. Constraints and uncertainty OpenSSL currently returns the time as a time_t value interpreted as UTC, discarding any timezone offset present in the ASN.1 TIME field. Some
debian