sdbbs
commented
1 year ago Ok, I found also https://github.com/wallix/redemption/blob/future/docs/manual_to_redemption.rst - this explains a bit more:
Redemption is a versatile RDP proxy, meaning one will connect to remote desktops through Redemption. This allows to centralize remote connection creating a single end point for several desktops.
Running
For a local test, the usual options are
-nand-f. The first option prevents Redemption from forking in the background, and the second makes sure no other instance is running. ::$ sudo /usr/local/bin/rdpproxy -nfAnd now what ? If everything went ok, you should be facing a waiting daemon ! You need two more things; first a client to connect to Redemption, second a server with RDP running (a Windows server, Windows XP Pro, etc.).
Redemption uses a hook file to get its target, username and password. This file is in
utils/authhook.pyand as you noticed it is written in Python. Two dictionnaries are important, the first one stores passwords, the second one stores the targets.
Ok, so I guess that blue screen above is part of the "allows to centralize remote connection creating a single end point for several desktops"
Unfortunately, as far as authhook.py goes - How to use this project · Issue #25 · wallix/redemption:
The part about
authhook.pyis out of date and has been replaced bypassthrough.py. Currently, the internal bouncer module is not accessible without modification ofpassthrough.pyand only the interactive login is used.
Also, I've found rdpclient:
$ rdpclient --help
Usage: rdpclient [options]
-h, --help produce help message
-v, --version show software version
-t, --target-device=<address>
-u, --username=<username>
-p, --password=<password>
-P, --port=<port>
-a, --inactivity-time=<milliseconds> milliseconds inactivity before sreenshot
-m, --max-time=<milliseconds> maximum milliseconds before sreenshot
-s, --screen-output=<path> png screenshot path
-r, --record-path=<path> dump socket path
-V, --vnc[={on|off}] enable vnc instead of rdp
-l, --lcg[={on|off}] use LCGRandom
-b, --load-balance-info=<data>
-n, --ini=<path> load ini filename
-c, --cert-check=<number>
0 = fails if certificates doesn't match or miss.
1 = fails if certificate doesn't match, succeed if no known certificate
2 = succeed if certificates exists (not checked), fails if missing.
3 = always succeed.
--verbose=<verbosity>This at least has something that looks like target address, and even has a record path; however:
$ rdpclient --target_device="127.0.0.1"
Bad option at parameter 1 (--target_device=127.0.0.1)Why a "bad option"? How is "address" supposed to be formatted, then?
And how is one supposed to work with rdpclient?
jonathanpoelen
I have managed to successfully compile redemption on Ubuntu 20.04 ( see also https://unix.stackexchange.com/questions/734205/dh-install-cannot-find-files-tried-in-debian-buildtmp-but-files-exist-in-debi ), but now I realize, I have no idea how to use it.
What I'm interested in, is capturing my session with a remote PC as video. In the session, I run a couple of graphics/CPU intensive apps, so if I start a screen capture like OBS Studio along with remote desktop (VNC or RDP) everything grinds down to a halt. The remote PC is Windows 10, so RDP is behaving a lot more responsive (as far as I can see desktop decorations etc are removed) even when the intensive applications run, and this is why I want to try capturing the RDP session as video.
I have seen in the README that there are possibilities to capture an RDP session to a video, but I don't get how/what I have to set up, to get a connection to my target server, and capture that session as a video.
Yes, I have seen How to use this project · Issue #25 · wallix/redemption, and I'm still not getting it.
Yes, I have, multiple times - still not getting it.
So, I can see there is a program
rdpproxy. Just by the naming, I would have imagined, it would have had a local port (maybe 3389), and then I'd specify target address and port - and then I could use my preferred RDP software (remmina) to connect to the proxy, which would have then forwarded/proxied usernames/passwords and traffic between my remmina on my Ubuntu, and the target remote server; and while doing that, it could have captured something that could be converted to video.However, that is not how things work; for one:
...
rdpproxyhas no command options for setting any ports.So, the readme says:
Ok, I did that on the PC, say, 192.168.0.10; and then from 192.168.0.12 I run
remmina, and intiate RDP connection to 192.168.0.10:3389; I get this:Ok, I did not expect this; what makes this screen,
passthrough.pyorrdpproxy -nf?In any case, one of those programs creates the screen - so what does that mean, that
rdpproxyproxies 127.0.0.1 to ... 127.0.0.1?Well, that is all fine as a starting example, however it should have been written in the README what should be expected of this example.
But then, good that I know how the example works now - but how do I use this for my use case? That is, how do I proxy 127.0.0.1 (current machine) to public IP of remote machine, as in example.com:3389? How can I specify a target port that is not 3389 but maybe due to port forwarding it is, say, 13389 (so, example.com:13389)? And how do I capture a video (or rather, as per README, a
.mwrmor.wrmlog file, which can thereafter be converted to video)?If
rdpproxycannot be used directly for this purpose, are there other programs in this project that could be used instead?