View Issue Details

IDProjectCategoryView StatusLast Update
0004463Kali LinuxGeneral Bugpublic2020-12-01 10:48
Reportercrash Assigned Tosbrun  
Status resolvedResolutionfixed 
Product Version2017.3 
Fixed in Version2018.1 
Summary0004463: mitmproxy does not start

mitmproxy does not start.

Steps To Reproduce


Traceback (most recent call last):
File "/usr/bin/mitmproxy", line 11, in <module>
load_entry_point('mitmproxy==2.0.2', 'console_scripts', 'mitmproxy')()
from construct import (Array, Bytes, Struct, UBInt16, UBInt32, UBInt8, PascalString, Embed, TunnelAdapter, GreedyRange, Switch, OptionalGreedyRange, Optional)
ImportError: cannot import name 'UBInt16'

Additional Information

apt search mitmproxy

mitmproxy/kali-rolling,kali-rolling,now 2.0.2-0kali2 all [installed,automatic]
SSL-capable man-in-the-middle HTTP proxy

uname -a

Linux Anubis 4.14.0-kali3-amd64 0000001 SMP Debian 4.14.12-2kali1 (2018-01-08) x86_64 GNU/Linux

python -V

Python 2.7.14+

I tried to upgrade the construct pkt but no success.




2018-01-11 08:21

administrator   ~0007786

The Debian bug report you show is an old one where the problem had been fixed by downgrading construct from 2.8.8 to 2.5.2. But construct switched to 2.8.16 at the end of November.

It looks like mitmproxy will need upstream changes to adapt to the new version of construct.

A bug had been opened about this:

So it looks like fixed in the 3.0.0~rc2... but updating to this version is likely also going to break some reverse dependencies which are not ready for this new version yet.

The commit adding compatibility with the new version of construct is this one:

It needs to be adapted as some of filenames look like different from what is in 2.0.2.



2018-01-11 09:02

manager   ~0007791

fixed in new version 2.0.2-0kali3

Issue History

Date Modified Username Field Change
2018-01-09 17:04 crash New Issue
2018-01-11 08:21 rhertzog Note Added: 0007786
2018-01-11 08:22 rhertzog Assigned To => sbrun
2018-01-11 08:22 rhertzog Status new => assigned
2018-01-11 09:02 sbrun Status assigned => resolved
2018-01-11 09:02 sbrun Resolution open => fixed
2018-01-11 09:02 sbrun Fixed in Version => 2018.1
2018-01-11 09:02 sbrun Note Added: 0007791
2020-12-01 10:48 g0tmi1k Priority high => normal