FreeRDP: ERROR: LeakSanitizer: detected memory leaks while trying to connect using gateway

Describe the bug Finally i wanted to be able to connect to my company using my linux box, but whatever i did faild. This time ive tried your freerdp nightlybuild on my debian testing (buster) but still was unable to connect…

To Reproduce Steps to reproduce the behavior:

1. Go to https://ci.freerdp.com/job/freerdp-nightly-binaries/
2. Click on follow the instructions to install it
3. try to connect with is

Expected behavior Some connection

Screenshots

$ /opt/freerdp-nightly/bin/xfreerdp /v:servername '/gu:domain\username' '/u:domain\username' /g:gateway
[10:21:12:142] [6825:6826] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
GatewayPassword: 
[10:21:17:233] [6825:6826] [ERROR][com.freerdp.core.nego] - Protocol Security Negotiation Failure
[10:21:17:233] [6825:6826] [ERROR][com.freerdp.core] - freerdp_set_last_error ERRCONNECT_SECURITY_NEGO_CONNECT_FAILED [0x0002000C]
[10:21:17:233] [6825:6826] [ERROR][com.freerdp.core.connection] - Error: protocol security negotiation or connection failure

=================================================================
==6825==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 112 byte(s) in 1 object(s) allocated from:
    #0 0x7fa263894cf8 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1cf8)
    #1 0x7fa25e0602c8 in CRYPTO_zalloc (/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1+0x16c2c8)

Indirect leak of 56 byte(s) in 1 object(s) allocated from:
    #0 0x7fa263894cf8 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1cf8)
    #1 0x7fa25e0602c8 in CRYPTO_zalloc (/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1+0x16c2c8)

SUMMARY: AddressSanitizer: 168 byte(s) leaked in 2 allocation(s).

** Application details

• Version of FreeRDP $ /opt/freerdp-nightly/bin/xfreerdp --version This is FreeRDP version 2.0.0-dev3 (b34e3bcf7)
• Command line used /opt/freerdp-nightly/bin/xfreerdp /v:servername '/gu:domain\username' '/u:domain\username' /g:gateway
• output of /buildconfig its your buld
• OS version connecting to windows server 2012 r2
• If available the log output from a run with /log-level:trace

Desktop (please complete the following information):

• OS: Debian testing amd64 (buster) the rest of the questions was not rellevant

Additional context Add any other context about the problem here. I dont think tho

Thank you for reporting a bug! thank you for fixing it;)