| Vulnerabilities | |||||
|---|---|---|---|---|---|
| Version | Suggest | Low | Medium | High | Critical |
300.6.0+3.6.2 - This version is safe to use because it has no known security vulnerabilities at this time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform
Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.
MIT - MIT LicenseThis crate contains the logic to build OpenSSL and is intended to be consumed by
the openssl-sys crate. You likely in theory aren't interacting with this too
much!
This crate follows the latest minor and patch versions for each maintained major version, according to the OpenSSL release strategy. It has no specific support for LTS versions.
The crate versions follow the X.Y.Z+B pattern:
X is the upstream OpenSSL API/ABI compatibility version:
300 for 3.Y.ZY and patch Z versions are incremented when making changes
to the crate, either OpenSSL update or internal changes.B contains the full upstream OpenSSL version, like 1.1.1k or 3.0.7.
Note that this field is actually ignored in comparisons and only there for
documentation.Building OpenSSL for windows-msvc targets, users can choose whether to enable
assembly language routines, which requires nasm.
The build process will automatically detect whether nasm.exe is installed in
PATH. If found, the assembly language routines will be enabled (in other words,
the no-asm option will NOT be configured).
You can manipulate this behavior by setting the OPENSSL_RUST_USE_NASM environment
variable:
1: Force enable the assembly language routines. (panic if nasm.exe is not
available.)0: Force disable the assembly language routines even if the nasm.exe can be
found in PATH.nasm.exe is
installed. If found, enable. If not, disable.However, this environment variable does NOT take effects on non-windows platforms.
This project is licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in openssl-src by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.