A RDP (Remote Desktop Protocol) proxy.
(A RDP client in projects/ClientQtGraphicAPI
, a RDP web client in projects/jsclient
)
Support of:
To compile ReDemPtion you need the following packages:
apt install libboost-tools-dev libboost-test-dev libssl-dev libkrb5-dev libsnappy-dev libpng-dev
Submodule ($ git submodule update --init
):
apt install libavcodec-dev libavformat-dev libavutil-dev libswscale-dev libx264-dev
And set the build variables (optionally)
FFMPEG_INC_PATH=/my/ffmpeg/include/path
FFMPEG_LIB_PATH=/my/ffmpeg/library/path
(/!\ without /
terminal)FFMPEG_LINK_MODE=shared
(static or shared, shared by default)Disable ffmpeg with NO_FFMPEG=1
.
Well, that's pretty easy once you installed the required dependencies.
Just run (as user):
$ bjam
or bjam toolset=your-compiler
(ex: bjam toolset=gcc
) (see https://boostorg.github.io/build/manual/develop/index.html#bbv2.overview.configuration and tools/bjam/user-config.jam
)
Verbose tests:
$ export REDEMPTION_LOG_PRINT=1
$ bjam tests
REDEMPTION_LOG_PRINT=e
for error and debug onlyREDEMPTION_LOG_PRINT=d
for debug onlyREDEMPTION_LOG_PRINT=w
for other than infoNote: bjam tests.norec
, bjam tests/front.norec
execute files directly in tests directory, but not recursively.
Compile executables without tests (as user):
$ bjam exe libs
and install (as administrator):
# bjam install
Binaries are located by default in /usr/local/bin
. For a user install, see setting build variables.
Use bjam --help
for more information.
REDEMPTION_FILTER_ERROR
: Only with BOOST_STACKTRACE=1
. no backtrace for specific error (see src/core/error.hpp
). example: export REDEMPTION_FILTER_ERROR=ERR_TRANSPORT_NO_MORE_DATA,ERR_SEC
.List with sed -E 's/.*\[ setvar ([^ ]+).*\] ;/\1/;t;d' jam/defines.jam
bjam -s FFMPEG_INC_PATH=$HOME/ffmpeg/includes ...
Or with a shell variable
export FFMPEG_INC_PATH=$HOME/ffmpeg/includes
bjam ....
List default values with sed -E 's/^([A-Z_]+)_DEFAULT [^=]+= (.*) ;/\1 = \2/;t;d' jam/defines.jam
$ bjam [variant=]{release|debug|san} [-s cxx_option=value] [target...]
release
: default
debug
: debug mode
san
: debug + enable sanitizers: asan, lsan, usan
-s cxx_color
: default auto never always
-s cxx_lto
: off on fat linker-plugin
-s cxx_relro
: default off on full
-s cxx_stack_protector
: off on strong all
...
(cxx_*
options list with sed -E 's/^constant jln_[^[]+\[ jln-get-env ([^ ]+) : ([^]]+) \].*/\1 = \2/;t;d' jam/cxxflags.jam
)
To test it, executes:
$ python tools/passthrough/passthrough.py
# /usr/local/bin/rdpproxy -nf
Now, at that point you'll just have two servers waiting for connections not much fun. You still have to run some RDP client to connect to proxy. Choose whichever you like xfreerdp, rdesktop, remmina, tsclient on Linux or of course mstsc.exe if you are on windows. All are supposed to work. If some problem occurs just report it to us so that we can correct it.
Example with freerdp when the proxy runs on the same host as the client:
$ xfreerdp /v:127.0.0.1
$ xfreerdp /v:127.0.0.1 /u:username@target_ip /p:password
A dialog box should open in which you can type a username and a password. With default passthrough.py at least internal services should work. Try login: internal, password: internal and bouncer2 or card as device. If you want to provide such extensions to current passthrough.py, please contribute it, it will be much appreciated.
$ xfreerdp /u:internal@internal /p:internal 127.0.0.1
.mwrm
and .wrm
are native capture formats in capture_flags=2
in rdpproxy.ini
.
redrec -f --video-codec mp4 -i file.mwrm -o output_prefix
Note: rdpproxy --print-default-ini
show a default ini file.
When create a new test or when a target fail with link error:
bjam targets.jam
for updated targets.jam
and projects/ClientQtGraphicAPI/redemption_deps.jam
files.
Or run ./tools/bjam/gen_targets.py > targets.jam
Specific deps (libs, header, cpp, etc) in ./tools/bjam/gen_targets.py
.
Proxy recorder is a tools used to record dialog between a client and an RDP server without any modification of the data by redemption. This allows to record reference traffic for replaying it later. It is useful for having available new parts or the RDP protocol in a reproducible way and replaying traffic when implementing the new orders. This tools is not (yet) packaged with redemption and delivered as stand-alone.
It can be compiled using static c++ libraries (usefull to use the runtime on systems where reference compiler is older) using the command line below. Links with openssl and kerberos are still dynamic and using shared libraries.
bjam -a -d2 toolset=gcc-7 proxy_recorder linkflags=-static-libstdc++
Exemple call line for proxy_recorder:
proxy_recorder --target-host 10.10.47.252 -p 3389 -P 8000 --nla-username myusername --nla-password mypassword -t dump-%d.out
./tools/packager.py --build-package
--force-target target
: target is a file in packaging/targets--force-build
./tools/packager.py --update-version 1.2.7 --git-tag --git-push-tag --git-push
(docs/TU/unit_test.pdf
)
Based on Boost.Test with a RED_
prefix rather than BOOST_
.
Redemption extra macro (tests/includes/test_only/test_framework/
):
RED_TEST(a == b)
, RED_REQUIRE
. (old macros: RED_CHECK_EQ(a,b)
, RED_REQUIRE_EQ(a,b)
, *_{LT,GT,LE,GE,NE,EQUAL})
RED_FILE_CONTENTS(filename, contents)
require #include "test_only/get_file_contents.hpp"
RED_TEST_DELEGATE_PRINT(type, expr)
: ex RED_TEST_DELEGATE_PRINT(myvalue, x.get())
RED_TEST_DELEGATE_PRINT_ENUM(type)
RED_CHECK_EQ_RANGES(rng1, rng2)
RED_TEST_FUNC(function)((args...) @ xxx)
: RED_TEST_FUNC(strlen)(("test") == 4)
RED_TEST_FUNC_CTX(function)
: auto fstrlen = RED_TEST_FUNC_CTX(function); RED_TEST(fstrlen("test") == 4)
RED_TEST_INVOKER(function)
: auto foo = RED_TEST_INVOKER(my_local_lambda_or_func) RED_TEST(foo("test") == 4)
RED_CHECK_EXCEPTION_ERROR_ID(stmt, id)
: CHECK_EXCEPTION_ERROR_ID(trans.send("message"_av), ERR_TRANSPORT_WRITE_FAILED)
RED_ERROR_COUNT
RED_BIND_DATA_TEST_CASE(name, dataset, varnames...)
RED_BIND_DATA_TEST_CASE(TestRdpLogonInfo, (std::array{
std::tuple{3, "3"},
std::tuple{5, "5"}
}), number, string)
{
RED_TEST(std::to_string(number) == string);
}
Special values:
RED_TEST(x == y +- 1_v); // x between y-1 to y+1
RED_TEST(x == y +- 3_percent); // x between y-y*3/100 to y+y*3/100
RED_TEST(x < y +- 1_v);
using namespace std::literals::string_view_literals;
// RED_TEST(render(range) == range) or RED_TEST(range == render(range))
RED_TEST(ut::ascii("aéc\xff"sv) == "abcd"sv); // no ascii character to hexadecimal ("a\xc3\xa9""c\xff")
RED_TEST(ut::utf8("aéc\xff"sv) == "abcd"sv); // no utf8 character to hexadecimal ("aéc\xff")
RED_TEST(ut::hex("aéc\xff"sv) == "abcd"sv); // all hexadecimal ("\x61\xc3\xa9\x63\xff")
RED_TEST(ut::dump("aéc\xff"sv) == "abcd"sv); // hexdump format
Special class:
tests/includes/test_only/working_directory.hpp
tests/includes/test_only/working_directory.hpp
RED_AUTO_TEST_CASE_WD(name, wd)
{
// wd is a WorkingDiretory
auto filename1 = wd.add_file("file1");
auto filename2 = wd.add_file("file2");
create_file(filename1);
create_file(filename2);
// RED_CHECK_WORKSPACE(wd); check if WorkingDiretory contains only file1 and file2 (implicit with RED_AUTO_TEST_CASE_WD)
}
RED_AUTO_TEST_CASE_WF(name, wf)
{
create_file(wf);
}
It is simple, more that could be thought at first sight, and bjam has the major feature over make to keep source directories clean, all build related informations for all architecture are kept together in bin directory.
The main drawback of bjam is the smaller user base.
But keeping in mind the complexity of make (or worse autotools + make), bjam is a great help. We also used to have an alternative cmake build system, but it was more complex than bjam and not maintained, so was removed.
Just edit config_spec.hpp (projects/redemption_configs/configs_specs/configs/specs/config_spec.hpp
).
The necessary changes should be simple using the surrounding code as exemple.
Then enter directory projects/redemption_configs
and type bjam
the needed files will be generated.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。