<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pkgsrc/net/mitmproxy, branch trunk</title>
<subtitle>[no description]</subtitle>
<id>https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk</id>
<link rel='self' href='https://git.osdyson.ru/mirror/pkgsrc/atom?h=trunk'/>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/'/>
<updated>2022-10-19T14:25:18Z</updated>
<entry>
<title>fighting a losing battle against the py-cryptography rustification, part 5</title>
<updated>2022-10-19T14:25:18Z</updated>
<author>
<name>nia</name>
<email>nia@pkgsrc.org</email>
</author>
<published>2022-10-19T14:25:18Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=53ecc4d90157aa0c296143896d09d4020fbc23f0'/>
<id>urn:sha1:53ecc4d90157aa0c296143896d09d4020fbc23f0</id>
<content type='text'>
Convert py-OpenSSL users to versioned_dependencies.mk</content>
</entry>
<entry>
<title>mitmproxy: Update to 8.1.1</title>
<updated>2022-07-08T12:57:26Z</updated>
<author>
<name>leot</name>
<email>leot@pkgsrc.org</email>
</author>
<published>2022-07-08T12:57:26Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=40a1e75a35a996f578e8a5f3c9f9b476946521df'/>
<id>urn:sha1:40a1e75a35a996f578e8a5f3c9f9b476946521df</id>
<content type='text'>
pkgsrc changes:
 - Follow upstream requirements for py-cryptography (previously a workaround was
   added in order to avoid possible too new py-cryptography that was not yet
   present in pkgsrc)

Changes:
8.1.1
-----
* Support specifying the local address for outgoing connections
* Fix a bug where an excess empty chunk has been sent for chunked HEAD request.
* Drop pkg_resources dependency.
* Fix huge (&gt;65kb) http2 responses corrupted.
* Remove overambitious assertions in the HTTP state machine,
  fix some error handling.</content>
</entry>
<entry>
<title>*: Revbump packages that use Python at runtime without a PKGNAME prefix</title>
<updated>2022-06-30T11:18:01Z</updated>
<author>
<name>nia</name>
<email>nia@pkgsrc.org</email>
</author>
<published>2022-06-30T11:18:01Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=c8c52b1eaa9f02980199a8b4bc92344ac344e087'/>
<id>urn:sha1:c8c52b1eaa9f02980199a8b4bc92344ac344e087</id>
<content type='text'>
</content>
</entry>
<entry>
<title>mitmproxy: Update to 8.1.0</title>
<updated>2022-06-18T20:40:17Z</updated>
<author>
<name>leot</name>
<email>leot@pkgsrc.org</email>
</author>
<published>2022-06-18T20:40:17Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=5c59581e6485bcc4e0ed76849db25d0b8eaccaeb'/>
<id>urn:sha1:5c59581e6485bcc4e0ed76849db25d0b8eaccaeb</id>
<content type='text'>
pkgsrc changes:
 - Now needs Python&gt;=3.9 per upstream
 - Further relax py-cryptography needs (seems to runs fine also with older
   py-cryptography) because in pkgsrc we do not have yet cryptography&gt;=36.

Changes:
## 15 May 2022: mitmproxy 8.1.0

* Mostly a Bug fix release
* DNS support
* Mitmproxy now requires Python 3.9 or above.

## 19 March 2022: mitmproxy 8.0.0
### Major Changes

* Major improvements to the web interface
* Event hooks can now be async
* New `tls_{established,failed}_{client,server}` event hooks to record
  negotiation success/failure

### Security Fixes

* CVE-2022-24766: Fix request smuggling vulnerability reported by @zeyu2001</content>
</entry>
<entry>
<title>mitmproxy: convert to egg.mk</title>
<updated>2022-01-10T22:43:41Z</updated>
<author>
<name>wiz</name>
<email>wiz@pkgsrc.org</email>
</author>
<published>2022-01-10T22:43:41Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=7cbc5bce152e21f055eac16116a5f244ae9f779b'/>
<id>urn:sha1:7cbc5bce152e21f055eac16116a5f244ae9f779b</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Forget about Python 3.6</title>
<updated>2021-12-30T13:05:27Z</updated>
<author>
<name>adam</name>
<email>adam@pkgsrc.org</email>
</author>
<published>2021-12-30T13:05:27Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=2a4aa624ba67ab6f387f6ea74ed58116f72f8029'/>
<id>urn:sha1:2a4aa624ba67ab6f387f6ea74ed58116f72f8029</id>
<content type='text'>
</content>
</entry>
<entry>
<title>net: Replace RMD160 checksums with BLAKE2s checksums</title>
<updated>2021-10-26T11:05:20Z</updated>
<author>
<name>nia</name>
<email>nia@pkgsrc.org</email>
</author>
<published>2021-10-26T11:05:20Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=5beb42e7908c0a6e35f8cdbdcfb3a8112bb98aa4'/>
<id>urn:sha1:5beb42e7908c0a6e35f8cdbdcfb3a8112bb98aa4</id>
<content type='text'>
All checksums have been double-checked against existing RMD160 and
SHA512 hashes

Not committed (merge conflicts...):

net/radsecproxy/distinfo

The following distfiles could not be fetched (fetched conditionally?):

./net/citrix_ica/distinfo citrix_ica-10.6.115659/en.linuxx86.tar.gz
./net/djbdns/distinfo dnscache-1.05-multiple-ip.patch
./net/djbdns/distinfo djbdns-1.05-test28.diff.xz
./net/djbdns/distinfo djbdns-1.05-ignoreip2.patch
./net/djbdns/distinfo djbdns-1.05-multiip.diff
./net/djbdns/distinfo djbdns-cachestats.patch</content>
</entry>
<entry>
<title>net: Remove SHA1 hashes for distfiles</title>
<updated>2021-10-07T14:41:10Z</updated>
<author>
<name>nia</name>
<email>nia@pkgsrc.org</email>
</author>
<published>2021-10-07T14:41:10Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=2bd80ae0726e0259d3eabe526800b6835d880a10'/>
<id>urn:sha1:2bd80ae0726e0259d3eabe526800b6835d880a10</id>
<content type='text'>
</content>
</entry>
<entry>
<title>mitmproxy: Update to 7.0.3</title>
<updated>2021-09-16T11:52:19Z</updated>
<author>
<name>leot</name>
<email>leot@pkgsrc.org</email>
</author>
<published>2021-09-16T11:52:19Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=bcd487f5ae1724605755e08c169f00fca5b579d5'/>
<id>urn:sha1:bcd487f5ae1724605755e08c169f00fca5b579d5</id>
<content type='text'>
Changes:
7.0.3
-----
* CVE-2021-39214: Fix request smuggling vulnerabilities reported by @chinchila
* Expose TLS 1.0 as possible minimum version on older pyOpenSSL releases
* Fix compatibility with Python 3.10

7.0.2
-----
* Fix a WebSocket crash introduced in 7.0.1

7.0.1
-----
* Performance: Re-use OpenSSL contexts to enable TLS session resumption
* Disable HTTP/2 CONNECT for Secure Web Proxies to fix compatibility with
  Firefox
* Use local IP address as certificate subject if no other info is available
* Make it possible to return multiple chunks for HTTP stream modification
* Don't send WebSocket CONTINUATION frames when the peer does not send any
* Fix HTTP stream modify example.
* Fix a crash caused by no-op assignments to `Server.address`
* Fix a crash when encountering invalid certificates
* Fix a crash when pressing the Home/End keys in some screens
* Fix a crash when reading corrupted flow dumps
* Fix multiple crashes on flow export
* Fix a bug where ASGI apps did not see the request body
* Minor documentation improvements</content>
</entry>
<entry>
<title>mitmproxy: Update to 7.0.0</title>
<updated>2021-07-17T14:14:47Z</updated>
<author>
<name>leot</name>
<email>leot@pkgsrc.org</email>
</author>
<published>2021-07-17T14:14:47Z</published>
<link rel='alternate' type='text/html' href='https://git.osdyson.ru/mirror/pkgsrc/commit/?id=549c5095fe09f7f9146069d65e5e30a30eaf67ad'/>
<id>urn:sha1:549c5095fe09f7f9146069d65e5e30a30eaf67ad</id>
<content type='text'>
Changes:
## 16 July 2021: mitmproxy 7.0.0

### New Proxy Core (@mhils, [blog post](https://www.mitmproxy.org/posts/releases/mitmproxy7/))

Mitmproxy has a completely new proxy core, fixing many longstanding issues:

* **Secure Web Proxy:** Mitmproxy now supports TLS-over-TLS to already
  encrypt the connection to the proxy.
* **Server-Side Greetings:** Mitmproxy now supports proxying raw TCP
  connections, including ones that start with a server-side greeting (e.g. SMTP).
* **HTTP/1 – HTTP/2 Interoperability:** mitmproxy can now accept an
  HTTP/2 connection from the client, and forward it to an HTTP/1 server.
* **HTTP/2 Redirects:** The request destination can now be changed on
  HTTP/2 flows.
* **Connection Strategy:** Users can now specify if they want mitmproxy
  to eagerly connect upstream or wait as long as possible. Eager
  connections are required to detect protocols with server-side
  greetings, lazy connections enable the replay of responses without
  connecting to an upstream server.
* **Timeout Handling:** Mitmproxy will now clean up idle connections
  and also abort requests if the client disconnects in the meantime.
* **Host Header-based Proxying:** If the request destination is
  unknown, mitmproxy now falls back to proxying based on the Host
  header. This means that requests can often be redirected to mitmproxy
  using DNS spoofing only.
* **Internals:** All protocol logic is now separated from I/O
  (["sans-io"](https://sans-io.readthedocs.io/)).
  This greatly improves testing capabilities, prevents a wide array of
  race conditions, and increases proper isolation between layers.


### Additional Changes

* mitmproxy's command line interface now supports Windows (@mhils)

* The `clientconnect`, `clientdisconnect`, `serverconnect`,
  `serverdisconnect`, and `log` events have been replaced with new
  events, see addon documentation for details (@mhils)

* Contentviews now implement `render_priority` instead of
  `should_render`, allowing more specialization (@mhils)
* Addition of block_list option to block requests with a set status
  code (@ericbeland)
* Make mitmweb columns configurable and customizable (@gorogoroumaru)
* Automatic JSON view mode when `+json` suffix in content type (@kam800)
* Use pyca/cryptography to generate certificates, not pyOpenSSL (@mhils)
* Remove the legacy protocol stack (@Kriechi)
* Remove all deprecated pathod and pathoc tools and modules (@Kriechi)
* In reverse proxy mode, mitmproxy now does not assume TLS if no scheme
  is given but a custom port is provided (@mhils)
* Remove the following options: `http2_priority`,
  `relax_http_form_validation`, `upstream_bind_address`,
  `spoof_source_address`, and `stream_websockets`. If you depended on
  one of them please let us know.  mitmproxy never phones home, which
  means we don't know how prominently these options were used. (@mhils)
* Fix IDNA host 'Bad HTTP request line' error (@grahamrobbins)
* Pressing `?` now exits console help view (@abitrolly)
* `--modify-headers` now works correctly when modifying a header that
  is also part of the filter expression (@Prinzhorn)
* Fix SNI-related reproducibility issues when exporting to curl/httpie
  commands. (@dkasak)
* Add option `export_preserve_original_ip` to force exported command to
  connect to IP from original request.
  Only supports curl at the moment. (@dkasak)
* Major proxy protocol testing (@r00t-)
* Switch Docker image release to be based on Debian (@PeterDaveHello)
* Multiple Browsers: The `browser.start` command may be executed more
  than once to start additional browser sessions. (@rbdixon)
* Improve readability of SHA256 fingerprint. (@wrekone)
* Metadata and Replay Flow Filters: Flows may be filtered based on
  metadata and replay status. (@rbdixon)
* Flow control: don't read connection data faster than it can be
  forwarded. (@hazcod)
* Docker images for ARM64 architecture (@hazcod, @mhils)
* Fix parsing of certificate issuer/subject with escaped special
  characters (@Prinzhorn)
* Customize markers with emoji, and filters: The `flow.mark` command
  may be used to mark a flow with either the default "red ball" marker,
  a single character, or an emoji like `:grapes:`.  Use the `~marker`
  filter to filter on marker characters. (@rbdixon)
* New `flow.comment` command to add a comment to the flow. Add
  `~comment &lt;regex&gt;` filter syntax to search flow comments. (@rbdixon)
* Fix multipart forms losing `boundary` values on edit. (@roytu)
* `Transfer-Encoding: chunked` HTTP message bodies are now retained if
  they are below the stream_large_bodies limit. (@mhils)
* `json()` method for HTTP Request and Response instances will return
  decoded JSON body. (@rbdixon)
* Support for HTTP/2 Push Promises has been dropped. (@mhils)
* Make it possible to set sequence options from the command line. (@Yopi)</content>
</entry>
</feed>
