By the way, the digital signature for the custom builds didn't even change. It's still the same Code Signing certificate issued by Comodo/Sectigo that we used since the last year including for version 6.
for the agent I only change the server and port our server and port 5656
for the host, an authorization password
As is clear from your report in the neighbouring thread - it is Eset that incorrectly treats our digital signature as being "compromised" and so deletes the files signed with it. This detection has nothing to do with their "unsafe" detection which only warns the user of a potential threat.
Vanilla installers are not deleted because they are signed with another (EV) certificate, also issued to "Remote Utilities LLC".
I'm afraid that in that message you cited Eset techs were confusing a signature being compromised (i.e. stolen and used by someone else to sign files, including malware files) versus a legit and signed file being integrated into a malware package (which is expected - any remote access software is abused that way). These are very different things.
We have already asked Eset for proof. Namely, we asked them to show us a file signed with our digital signature that would have a trojan or other malware inside. No one can "insert" a trojan or malware into a signed file without breaking/invalidating its signature and folks at Eset know that well. We are curious to see at least one such file - after all such bold claims must be supported by firm evidence.