Closed Chomikmarkus closed 3 years ago
PyRDP doesn't do the network-level monster-in-the-middle (MITM) attack on its own. You need another tool to do that. You can use bettercap to achieve ARP poison and combine it with L3 transparent proxying to achieve that. Read more about transparent proxying here.
To start with a simpler test, the client should connect to the pyrdp machine 82.221.123.4 and you should run pyrdp-mitm.py
with:
pyrdp-mitm.py 82.221.123.56
We are tracking the fact that we could simplify the setup via issue #266.
Thanks gonna take a look,and come back to you!
Hello! Have installed pyrdp on my VPS machine, (with ip82.221.123.4, for example) On my another VPS machine(same subnet,with ip:82.221.123.56, for example) i installed xrdp! So running next command: pyrdp-mitm.py 82.221.123.56 --- no output or whatever kind reaction from pyrdp when i log to my machine xrdp session same situation is when i run it with docker container!