Update aioquic dependency to >= 1.0.0, < 2.0.0 (fixes: #6746) (#6747)

#### Description

This fixes some specification compliance issues as well as a potential
DoS vulnerability.

Start with version 1.0.0, aioquic follows semantic versioning, so no
breaking changes will occur before version 2.0.0.

#### Checklist

 - [x] I have updated tests where applicable.
 - [x] I have added an entry to the CHANGELOG.
This commit is contained in:
Jeremy Lainé 2024-03-20 21:31:03 +01:00 committed by GitHub
parent a26013908a
commit 0d68e193b1
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 3 additions and 1 deletions

View File

@ -15,6 +15,8 @@
([#5370](https://github.com/mitmproxy/mitmproxy/pull/5370), @zioalex)
* Make it possible to read flows from stdin with mitmweb.
([#6732](https://github.com/mitmproxy/mitmproxy/pull/6732), @jaywor1)
* Update aioquic dependency to >= 1.0.0, < 2.0.0.
([#6747](https://github.com/mitmproxy/mitmproxy/pull/6747), @jlaine)
## 07 March 2024: mitmproxy 10.2.4

View File

@ -31,7 +31,7 @@ classifiers = [
# https://packaging.python.org/en/latest/discussions/install-requires-vs-requirements/#install-requires
# It is not considered best practice to use install_requires to pin dependencies to specific versions.
dependencies = [
"aioquic>=0.9.24,<0.10",
"aioquic>=1.0.0,<2.0.0",
"asgiref>=3.2.10,<3.8",
"Brotli>=1.0,<1.2",
"certifi>=2019.9.11", # no semver here - this should always be on the last release!