Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    saalmaan
    @saalmaan
    when you install mitmproxy v 0.17, does it work?
    Marcus Bointon
    @SynchroM_twitter
    No. I have to install it with --upgrade to force it to upgrade, but then tamper.py fails with this error: s{"msg": {"errorCode": 101, "errorDesc": "Could not start proxy, error loading libraries", "method": "proxy-error"}}
    mitmproxy works fine by itself
    either version
    saalmaan
    @saalmaan
    interesting, if you uninstall mitmproxy, and to pip install tamper, it will auto install all its dependencies including mitmproxy
    Marcus Bointon
    @SynchroM_twitter
    yes, that works, but the chrome ext still doesn't see it.
    saalmaan
    @saalmaan
    ok cool
    chrome extension continue to say cannot connect to proxy error?
    Marcus Bointon
    @SynchroM_twitter
    I think I found a problem with a port clash
    saalmaan
    @saalmaan
    just change the port to 8181 and see if that works in chrome extension
    Marcus Bointon
    @SynchroM_twitter
    I tried that - does the chrome ext start mitmproxy, or do I need to do that manually? I tried clicking the restart button in settings, but nothing happens
    mitmproxy isn't running
    saalmaan
    @saalmaan
    chrome extension auto start/connects with mitmproxy on the port you mention, you dont have have to run mitmproxy manually
    Marcus Bointon
    @SynchroM_twitter
    If I run mitmproxy manually it still fails to connect - if I configure chrome to talk to it directly, it works fine
    on port 8080
    saalmaan
    @saalmaan
    when you have chrome open and enable tamper extension, and then try to run mitmproxy manually it wont work because chrome extension has taken over the default port 8080, mitmproxy fails because of that
    as I said earlier tamer chrome extension auto manages the mitmproxy behind the scenes
    are you see an error similar to this?
    dutzi/tamper#18
    Marcus Bointon
    @SynchroM_twitter
    If I disable/enable tamper in chrome when mitmproxy is not running, it doesn't start and there are no errors other than 'Could not connect to proxy'. After this I can still start mitmproxy on port 8080 manually, indicating that nothing is using it.
    and if i kill it and restart tamper again, it still doesn't start
    it might be useful if tamper could log errors to the console
    saalmaan
    @saalmaan
    yeah, you are right, with log, its really hard to debug it
    Marcus Bointon
    @SynchroM_twitter
    I've been messing with other proxies - mitmproxy (manual), burp, ZAP - and they all work fine. I was hoping to get the better integration with tamper though.
    saalmaan
    @saalmaan
    tamper has dependency on mitm, I can tell you if you get it working, tamper is best tool in developers arsenal
    let me check if mac console spits out any log
    Marcus Bointon
    @SynchroM_twitter
    I've used mitmproxy for a couple of years
    I'll look there
    Marcus Bointon
    @SynchroM_twitter
    nope, no system console errors
    saalmaan
    @saalmaan
    ok found tamer log file
    go to chrome://extensions/
    tick developer mode
    Look for Tamper, click the "background page" link
    Go to Console
    Click Cmd+R
    This message was deleted
    saalmaan
    @saalmaan
    Screen Shot 2016-08-03 at 17.03.26.png
    what do you see?
    Marcus Bointon
    @SynchroM_twitter
    It's repeating "connecting to proxy" then "Disconnected"
    saalmaan
    @saalmaan
    mine is
    connecting to proxy background.js:1 Got message: Object {method: "hello"} background.js:1 Got message: Object {version: "0.24.5", method: "version"} background.js:1 Mitmproxy Extension Version: 0.24.5 background.js:1 Proxy Log: Starting proxy... (8080) background.js:1 Got message: Object {method: "start-proxy", port: "8080"} background.js:1 Got message: Object {rules: Array[5], method: "update-rules"} background.js:1 Got message: Object {method: "proxy-started"}
    Marcus Bointon
    @SynchroM_twitter
    there is nothing running on port 8080 - it rejects the connection if I telnet to it
    sodacrackers
    @sodacrackers
    sorry if it's been answered 50 times..... I've installed the Chrome Extension but no luck running it..... Doesn't seem to start mitmproxy within the Chrome Extension..... Is there a quick fix? Thank you.
    Ryan Baer
    @ryanbaer
    @sodacrackers did you get it working?
    Tri Le
    @trile
    This looks like a very promising product. Too sad it is outdated as of today. I am so close to have this working on MacOS Sierra. I got Chrome Extension connected with tamper.py and mitmproxy following the this thread dutzi/tamper#23. However I found out that mitmproxy version 0.11 is outdated and properly generated the cert with SHA-1 algorithm. Google Chrome had move to SHA-2 since version 56. I have Chrome 60 so it generate the message "Security certificate is signed using a weak signature algorithm". I have tried to generate the new cert from a newer version of mitmproxy but it was not compatible with tamper.py.
    Ryan Baer
    @ryanbaer
    @trile that sounds like a good opportunity to do a PR and bring things up to date. It looks like the owner is still active on Github and would likely welcome a PR
    Tri Le
    @trile
    @ryanbaer thanks for the suggestion. Yes, I guess I'll dig in a code to see how it will work with the new mitmproxy. I just came back to engineering recently after about seven-year-break so I need to brush up my Python a bit :)
    Ryan Baer
    @ryanbaer
    @trile sounds good. let me know if you wanna talk anything out or collab on it
    Ben Creasy
    @jcrben
    looks like @dutzi took the link to this chat off in 2018 dutzi/tamper@c6f6da9
    Ben Creasy
    @jcrben
    seems like there needs to be a maintained fork