Thought one of the message stated connection was unexpectedly closed by server, so though finding out why would help.
Pegasus use to use the ssl dll files separately, so installing newer ones would update it.
But now it is compiled into the program. It is currently at 1.1.1k as far as I know. There were updates within that version, but don't recall what last was.
They did a jump from 1 to 3, so my linux is currently using
openssl-3.5.7-2.fc43.x86_64
So, not sure what all has changed between 1.1.1k and 3.5.7-2?
Google AI comes up with this.
The jump from OpenSSL 1.1.1k to OpenSSL 3.5.7-2 marks a massive architectural, performance, and feature transformation. It bypasses version 2.0 entirely, as the OpenSSL project jumped straight to 3.0 to signal major breaking API updates.
Here are the key differences broken down by category:
Architecture & API Changes
The Provider Model: OpenSSL 3.x introduced a "Provider" architecture. Algorithms are now treated as modules (e.g., Default, Legacy, FIPS) rather than being hardcoded into the core library.
API Deprecation: All legacy, low-level cryptographic functions (like AES_encrypt or SHA256_Update) are completely deprecated. Developers are forced to use the high-level EVP API.
Opaque Structures: Many public data structures have been made internal/opaque to increase safety. You can no longer stack-allocate them; they must be heap-allocated via setter and getter functions.
Version Scheme: OpenSSL moved to a standard MAJOR.MINOR.PATCH system. API and ABI compatibility are now explicitly guaranteed across the same Major version (all 3.x releases).
Protocol & Algorithm Upgrades
QUIC Protocol: OpenSSL 3.x introduces native client-side support for the QUIC transport protocol (RFC 9000). Version 1.1.1 only supported TLS and DTLS.
FIPS 140-3 Compliance: Version 1.1.1 utilized an outdated FIPS module. The 3.x series introduces a natively validated FIPS provider meeting modern cryptographic standards.
Modern Cryptography: Massive additions include support for Post-Quantum Cryptography (like ML-KEM/ML-DSA), Encrypted Client Hello (ECH), and Certificate Management Protocol (CMP).
Performance & Stability
Handshake Latency: Interestingly, because of the extra software abstraction layer introduced by the provider framework, OpenSSL 3.x can experience slightly higher TLS handshake latency compared to 1.1.1 when using Elliptic Curve (EC) algorithms.
Threading: Multi-threading capabilities are cleaner and inherently safer due to modern RNG upgrades and decoupled providers.
Support Status
OpenSSL 1.1.1k: This version is fully End-of-Life (EOL). It does not receive public security patches or bug fixes, making it a high security risk.
OpenSSL 3.5.7-2: This is the current, actively supported Long-Term Support (LTS) branch, fully patched against modern vulnerabilities.
So, it is what it is. Also, with linux it is using the 64bit version. So for info.
Thought one of the message stated connection was unexpectedly closed by server, so though finding out why would help.
Pegasus use to use the ssl dll files separately, so installing newer ones would update it.
But now it is compiled into the program. It is currently at 1.1.1k as far as I know. There were updates within that version, but don't recall what last was.
They did a jump from 1 to 3, so my linux is currently using
openssl-3.5.7-2.fc43.x86_64
So, not sure what all has changed between 1.1.1k and 3.5.7-2?
Google AI comes up with this.
The jump from OpenSSL 1.1.1k to OpenSSL 3.5.7-2 marks a massive architectural, performance, and feature transformation. It bypasses version 2.0 entirely, as the OpenSSL project jumped straight to 3.0 to signal major breaking API updates.
Here are the key differences broken down by category:
Architecture & API Changes
The Provider Model: OpenSSL 3.x introduced a "Provider" architecture. Algorithms are now treated as modules (e.g., Default, Legacy, FIPS) rather than being hardcoded into the core library.
API Deprecation: All legacy, low-level cryptographic functions (like AES_encrypt or SHA256_Update) are completely deprecated. Developers are forced to use the high-level EVP API.
Opaque Structures: Many public data structures have been made internal/opaque to increase safety. You can no longer stack-allocate them; they must be heap-allocated via setter and getter functions.
Version Scheme: OpenSSL moved to a standard MAJOR.MINOR.PATCH system. API and ABI compatibility are now explicitly guaranteed across the same Major version (all 3.x releases).
Protocol & Algorithm Upgrades
QUIC Protocol: OpenSSL 3.x introduces native client-side support for the QUIC transport protocol (RFC 9000). Version 1.1.1 only supported TLS and DTLS.
FIPS 140-3 Compliance: Version 1.1.1 utilized an outdated FIPS module. The 3.x series introduces a natively validated FIPS provider meeting modern cryptographic standards.
Modern Cryptography: Massive additions include support for Post-Quantum Cryptography (like ML-KEM/ML-DSA), Encrypted Client Hello (ECH), and Certificate Management Protocol (CMP).
Performance & Stability
Handshake Latency: Interestingly, because of the extra software abstraction layer introduced by the provider framework, OpenSSL 3.x can experience slightly higher TLS handshake latency compared to 1.1.1 when using Elliptic Curve (EC) algorithms.
Threading: Multi-threading capabilities are cleaner and inherently safer due to modern RNG upgrades and decoupled providers.
Support Status
OpenSSL 1.1.1k: This version is fully End-of-Life (EOL). It does not receive public security patches or bug fixes, making it a high security risk.
OpenSSL 3.5.7-2: This is the current, actively supported Long-Term Support (LTS) branch, fully patched against modern vulnerabilities.
So, it is what it is. Also, with linux it is using the 64bit version. So for info.
