| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
We've had a perpetual sequencing problem with addon startup. Users need to be
able to specify options to addons on the command-line, before addons are
actually loaded. This is only exacerbated with the new async core, where load
order can't be relied on.
This patch introduces deferred options. Options passed with "--set" on the
command line are deferred if they are unknown, and are automatically applied by
the addon manager once matching addons are registered and their options are defined.
|
|\
| |
| | |
Zap some commands.call invocations that were missed in the rename
|
|/ |
|
|\
| |
| | |
Remove leftover processing_complete
|
|/ |
|
|\
| |
| | |
Workaround for MacOS transparent proxy
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| | |
| | | |
This workaround (adopted from #1261) allows MacOS users to redirect their machine's outgoing traffic to mitmproxy transparently.
|
|\ \ \
| | | |
| | | | |
Remove allowremote addon, add an improved take called block
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We now have two options: block_global blocks global networks, block_private
blocks private networks. The block_global option is true by default, and
block_private is false by default. The addon name is "block" so the options are
correctly prefixed.
Also make option documentation precise, reduce verbosity of logs.
|
|\ \ \
| | | |
| | | | |
fix #3024
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Fix typo in addons-overview.md
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Remove custom events
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
These were always weird, and were added to support exit when processing
completed to mitmdump. We now have better ways to do this.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Revamp dup_and_replay example
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Exposes view.add as a command
- Copes with cases where a view addon isn't present
- Avoids infinite loop caused by replaying replays
Fixes #3096
|
|\ \ \ \ \ \
| |/ / / / /
|/| / / / /
| |/ / / / |
Remove the tick event
|
| | | | |
| | | | |
| | | | |
| | | | | |
Mitmproxy: the tickless wonder.
|
|\| | | |
| | | | |
| | | | | |
Redesign keepserving
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
We no longer use this anywhere, so ditch it.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
- Instead of listening for a pseudo-event, we periodically check whether client
replay, server replay or file reading is active.
- Adjust server replay not to
use tick.
- Adjust readfile to expose a command to check whether reading is in progress.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Also add a periodic refresh every 0.5 seconds for the statusbar. This is in
addition to refreshes upon event update notifications, and picks up replay
status changes not linked to flow events.
|
| | | | | |
|
| | | | | |
|
|\| | | |
| | | | |
| | | | | |
Revamp client replay
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Re-design the way client replay works. Before, we would fire up a thread,
replay, wait for the thread to complete, get the next flow, and repeat the
procedure. Now, we have one replay thread that starts when the addon starts,
which pops flows off a thread-safe queue. This is much cleaner, removes the
need for busy tick, and sets the scene for optimisations like server connection
reuse down the track.
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Changed syntax of two options (from v2 to v3)
|
| | | | |
| | | | |
| | | | |
| | | | | |
--client-certs = v2 syntax --> --set client_certs=value = v3 syntax
--cadir = v2 syntax --> --set cadir=value = v3 syntax
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
[requires.io] dependency update on master branch
|
| | | | | |
|
|/ / / / |
|
|\ \ \ \
| | | | |
| | | | | |
Fix #3002. Auto-expanding for tilda.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
add SO_KEEPALIVE
|
| | | | | | |
|
|\ \ \ \ \ \
| |_|/ / / /
|/| | | | | |
asyncio: shift script reloading out of the tick event
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The granularity of mtime is surprisingly bad. Make the tests more robust
against this, and promote has_log back to a public method, now that we have a
few legitimate examples.
|