mirror of
https://github.com/Grasscutters/mitmproxy.git
synced 2024-11-25 18:03:50 +00:00
docs: clarify binary packaage admonition
This commit is contained in:
parent
2db223decb
commit
56010ebcb7
@ -51,19 +51,18 @@ command line. The console interface is not supported on native Windows.
|
||||
|
||||
## Self-contained Pre-built Binary Packages
|
||||
|
||||
For some platforms we provide pre-built binary packages containing
|
||||
ready-to-run executables. This includes a self-contained Python 3
|
||||
environment, a recent OpenSSL that support ALPN and HTTP/2, and other
|
||||
dependencies that would otherwise we cumbersome to compile and install.
|
||||
For some platforms we provide pre-built binary packages containing ready-to-run
|
||||
executables. This includes a self-contained Python 3 environment, a recent
|
||||
OpenSSL that support ALPN and HTTP/2, and other dependencies that would
|
||||
otherwise we cumbersome to compile and install.
|
||||
|
||||
Please be advised that we do not update these binaries after the initial
|
||||
release. This means we do not include security-related updates of our
|
||||
dependencies in already released mitmproxy versions. If there is a
|
||||
severe issue, we might consider releasing a bugfix release of mitmproxy
|
||||
and corresponding binary packages.
|
||||
Dependencies in the binary packages are frozen on release, and can't be updated
|
||||
in situ. This means that we necessarily capture any bugs or security issues that
|
||||
may be present. We don't generally release new binary packages simply to update
|
||||
dependencies (though we may do so if we become aware of a really serious issue).
|
||||
If you use our binary packages, please make sure you update regularly to ensure
|
||||
that everything remains current.
|
||||
|
||||
We only support the latest version of mitmproxy with bugfix and security
|
||||
updates through regular minor releases.
|
||||
|
||||
## Docker Images
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user