IPVanish

最新版本 OpenSSL 1.1.1l (64-bit)

OpenSSL 1.1.1l (64-bit)

OpenSSL 1.1.1l (64-bit)
IPVanish 是世界上唯一真正的頂級 VPN 服務。這意味著它可以提供最好的 VPN 速度,最安全的連接和最具競爭力的價格。 VPN 網絡跨越 60 多個國家的 450 多個服務器上的 40,000 多個 IP,讓您能夠匿名瀏覽,並訪問全球每個角落的無限制互聯網.

IPVanish 為日常網絡使用提供安全的環境。一旦建立 VPN 連接,所有在線數據(電子郵件,即時消息,數據傳輸,網上銀行)都將通過加密隧道.

IPVanish VPN 特性:

超快速連接
“我們是唯一的頂級 VPN 網絡,意味著更快,更多“

100%在線安全
IPVanish 是保護自己免受網絡威脅和不安全的 Wi-Fi 熱點的最佳方式.

易於使用和免費軟件
簡單的點和點擊軟件為您的所有設備.

最好的 VPN Network
IPVanish 為 60 多個國家的 450 多台服務器提供了 40,000 多個 IP 的安全連接。虛擬地從世界任何地方訪問網頁.

注意:需要.NET Framework。無法在未註冊版本中更改您的 IP .

也可用:下載 IPVanish 為 Mac

ScreenShot

軟體資訊
檔案版本 OpenSSL 1.1.1l (64-bit)

檔案名稱 Win64OpenSSL-1_1_1L.exe
檔案大小
系統 Windows XP / Vista / Windows 7 / Windows 8 / Windows 10
軟體類型 未分類
作者 IPVanish Team
官網 https://www.ipvanish.com/
更新日期 2021-08-25
更新日誌

What's new in this version:

Fixed an SM2 Decryption Buffer Overflow:
- In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Typically an application will call this function twice. The first time, on entry, the "out" parameter can be NULL and, on exit, the "outlen" parameter is populated with the buffer size required to hold the decrypted plaintext. The application can then allocate a sufficiently sized buffer and call EVP_PKEY_decrypt() again, but this time passing a non-NULL value for the "out" parameter.
- A bug in the implementation of the SM2 decryption code means that the calculation of the buffer size required to hold the plaintext returned by the first call to EVP_PKEY_decrypt() can be smaller than the actual size required by the second call. This can lead to a buffer overflow when EVP_PKEY_decrypt() is called by the application a second time with a buffer that is too small.
- A malicious attacker who is able present SM2 content for decryption to an application could cause attacker chosen data to overflow the buffer by up to a maximum of 62 bytes altering the contents of other data held after the buffer, possibly changing application behaviour or causing the application to crash. The location of the buffer is application dependent but is typically heap allocated.

Fixed various read buffer overruns processing ASN.1 strings:
- ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING structure which contains a buffer holding the string data and a field holding the buffer length. This contrasts with normal C strings which are repesented as a buffer for the string data which is terminated with a NUL (0) byte.
- Although not a strict requirement, ASN.1 strings that are parsed using OpenSSL's own "d2i" functions (and other similar parsing functions) as well as any string whose value has been set with the ASN1_STRING_set() function will additionally NUL terminate the byte array in the ASN1_STRING structure.
- However, it is possible for applications to directly construct valid ASN1_STRING structures which do not NUL terminate the byte array by directly setting the "data" and "length" fields in the ASN1_STRING array. This can also happen by using the ASN1_STRING_set0() function.
- Numerous OpenSSL functions that print ASN.1 data have been found to assume that the ASN1_STRING byte array will be NUL terminated, even though this is not guaranteed for strings that have been directly constructed. Where an application requests an ASN.1 structure to be printed, and where that ASN.1 structure contains ASN1_STRINGs that have been directly constructed by the application without NUL terminating the "data" field, then a read buffer overrun can occur.
- The same thing can also occur during name constraints processing of certificates (for example if a certificate has been directly constructed by the application instead of loading it via the OpenSSL parsing functions, and the certificate contains non NUL terminated ASN1_STRING structures). It can also occur in the X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions.
- If a malicious actor can cause an application to directly construct an ASN1_STRING and then process it through one of the affected OpenSSL functions then this issue could be hit. This might result in a crash (causing a Denial of Service attack). It could also result in the disclosure of private memory contents (such as private keys, or sensitive plaintext).

OpenSSL 1.1.1l (64-bit) 相關參考資料
Changelog - OpenSSL

OpenSSL 1.1.1 — Changes between 1.1.1k and 1.1.1l [24 Aug 2021] ... Have 'config' recognise 64-bit mingw and choose 'mingw64' as the target platform ...

https://www.openssl.org

Download OpenSSL 1.1.0k (64-bit) Free - FileCombo

Download OpenSSL 1.1.0k (64-bit) for Windows PC from FileCombo. Fast update and Free Download Latest Version 2021 - FileCombo.

https://filecombo.com

Downloads - OpenSSL

A list of mirror sites can be found here. Note: The latest stable version is the 3.0 series. Also available is the 1.1.1 series which is our Long Term Support ( ...

https://www.openssl.org

OpenSSL

0 is now available: please download and upgrade! 24-Aug-2021, Security Advisory: two security fixes. 24-Aug-2021, OpenSSL 1.1.1l is now available, ...

https://www.openssl.org

OpenSSL (64-bit) - FileHorse

2021年8月25日 — Latest Version: OpenSSL 1.1.1l (64-bit) LATEST. Requirements: Windows XP64 / Vista64 / Windows 7 64 / Windows 8 64 / Windows 10 64.

https://www.filehorse.com

OpenSSL - 維基百科,自由的百科全書

TLS 1.3的開發由Akamai贊助。 主要版本釋出[編輯]. OpenSSL版本歷史 ...

https://zh.wikipedia.org

OpenSSL 1.1.1 and 3.0 x86x64 Binaries for Microsoft Windows

Microsoft Windows OpenSSL 1.1.1l and 3.0.0. 64-bit (Win64 / x64) and 32-bit (Win32 / x86) Binary Distribution. Digitally signed. Download for Free.

https://kb.firedaemon.com

OpenSSL 1.1.1 Series Release Notes

Major changes between OpenSSL 1.1.1k and OpenSSL 1.1.1l [24 Aug 2021] ... in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit ...

https://www.openssl.org

OpenSSL 1.1.1l (64-bit) - FileHorse

2021年8月25日 — OpenSSL 1.1.1l (64-bit). Date released: 25 Aug 2021 (4 weeks ago). Download · OpenSSL 1.1.1k (64-bit). Date released: 26 Mar 2021 (6 months ...

https://www.filehorse.com

version 1.1.1k - OpenSSL

Changes between 1.1.1l and 1.1.1m [xx XXX xxxx] *) Changes between 1.1.1k and ... [Richard Levitte] *) Have 'config' recognise 64-bit mingw and choose ...

https://www.openssl.org