[Windows] Config in Filename prone to problems

Great idea for making the Windows executable filename include the host and key, but I can see some problems with this (which I am sure you are aware of! :-)

I can tell you that a filename like rustdesk-host=rustdesk.mydomain.uk.exe is a "red rag to a bull" for the Windows security and anti-virus software which will immediately cause concern to the end user.

Forgive me if I am wrong, but in my experience any filename with more than 2 dots in will flag up suspicions (and quite rightly to!), a classic virus or malware trick.

Is there a way to make your software 'translate' a - dash to a period for the config?

e.g.

rustdesk-host=rustdesk-mydomain-uk.exe

... thereby only having 1 dot in the filename.

What do you think?

No files, tests, or entry points are named in the issue. Start by locating where the Windows executable filename and its host/key configuration are generated, then check how dots and dashes are handled. Done means the proposed filename behavior is evaluated and, if accepted, documented with an example such as rustdesk-host=rustdesk-mydomain-uk.exe.