Created attachment 143160 [details] Example incriminated file SUMMARY RDP files were defined by MSFT I guess. So they have the monopoly on what he should look like. And today, Azure VM generates automatically RDP files for you to log-in. But these files are not understood by KRDC STEPS TO REPRODUCE 1. Go to https://labs.azure.com/virtualmachines 2. Click on the "ms-DocumentCardActions-action action-111" button (Connect to the virtual machine) 3. Select "Connect via RDP" 4. Open the downloaded file with KRDC OBSERVED RESULT "The entered address [...]" EXPECTED RESULT FreeRDP window with the remote desktop WORKAROUND Take the username from the file (without the `username:s:`), add to it the URL from the file (without the `full address:s:`) and add it manually to the address bar or KRDC `blue@ml-lab-ff54a48f-c206-44ec-9330-ce7191ffa797.westeurope.cloudapp.azure.com:61055` SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION File example ``` full address:s:ml-lab-ff54a48f-c206-44ec-9330-ce7191ffa797.westeurope.cloudapp.azure.com:61055 prompt for credentials:i:1 username:s:blue ```
But krdc doesn't open *any* files, does it? I mean there's no open->file or anything, so the problem wouldn't be Azure RDP files, but RDP files at all?
Yep, same thing for access remote machines via CyberArk. In this case there's no workaround, as all the auth is handled by cyberark itself and saved rdp files are not reusable. In this case i'm forced to use Reminia, instread of preffered krdc.