Conrad Sallian's community posts

Hello Andreas,

Thank you for your message. This button should be clicked on the remote side, just once. For PRO license users, the window can also disappear after a 10-minute timeout.

Or do you mean that the window doesn’t go away even if the remote user clicks the OK button?

Hello Trent,

Thank you for the report.

However, the update has always worked that way, so it's strange that ESET suddenly decided to block that connection for this reason. Perhaps either their settings or policy have changed.

In this case, I would recommend contacting ESET to report the issue. You can reach their lab via email at samples@eset.sk, or, even better, post a message on their community forum: https://forum.eset.com/. If you are their customer, they are obligated to respond promptly and explain their actions.

Please, note that ESET might offer various explanations for not addressing the issue. These often sound like, "This program has been used in malicious activity" (in which case, ask them how a signed vanilla executable/installer is to blame for such activity). After all, there isn't a single remote access tool on the market that hasn't been used maliciously or for fraud activities.

Or they might say, "It was compromised" (compromised how? If the certificate was compromised, it should have been revoked, but it's still active). Lastly, they could claim, "It is used in cyberattacks as part of malware"—but isn’t it their responsibility to combat wrappers, droppers, and all sorts of 'ers,' while leaving legitimate (i.e., digitally signed) software intact?

Another favorite excuse of virtually any antivirus company is: "It violates the CSA guidelines." A simple question like, "Which specific CSA guideline does it violate?" usually results in frustration and an answer along the lines of, "We say it's a threat because we say so."

Hello Brad,

Thank you for your message.

Yes, that makes perfect sense. In fact, we would have implemented this earlier, but there are still some compatibility issues with older Windows HTTPS clients. The most practical solution is to implement HTTPS for newer versions of Windows (8 and later) as well as Windows Server, while still using HTTP on the older Windows versions.

Information Technology wrote:

Yep. What threw me off with that is Remote Utilities Pty (Cy) Ltd. didn't match Remote Utilities Pte. Ltd. that's on remoteutilities.com

Yes, I understand. We'll update it now. Thanks.

No problem. You can also directly check the domain ownership if you visit: https://remoteutilities.net/

Hello,

Yes, the domain is owned by our company and the link (you forgot httpS) leads to our file. You can check the file's digital signature, it should be EV-Code Signed by Remote Utilities.

However, we'll check the domains SSL certificate. Seems like there are some issues. We'll also check if it was blacklisted (for that reason) by any security providers. Thanks for letting us know.

Matthew, at the moment this issue can be fixed by enabling the 'Use group view' checkbox in the Viewer options. This option is turned on by default that's why many users couldn't notice this weird behavior. Thank you again for reporting.

Hello Matthew,

Thank you for the detailed report. Yes, indeed we managed to reproduce the issue. We will release a fix.

Hi Alex,

Thank you for your message.

It's important not to confuse address book sync with authentication on Hosts, as they serve two different purposes. Address book sync simply allows users to share 'shortcuts' to remote computers with certain properties. However, to actually access those computers, users still need to authenticate on them.

A good analogy is an address book of houses in a neighborhood. You can share the address book with people, but they still need the house key to enter any specific home.

If you're looking to revoke access when an employee leaves the company, you'll need to update the authentication settings on the relevant Hosts. The only authentication method that allows for centralized permission management is 'custom server security.' In this setup, you enable the authentication role on the RU Server, create users and groups, and set permissions. When an employee leaves, you can simply remove them from the group or delete their user account.

To sum it up: use address book sync to share address book records, and use 'custom server security' to set and manage authentication permissions centrally.

Hope that helps!

Dear Users,

We are pleased to announce the release of the final version 7.5.1.0. This beta discussion thread will now be closed. Please feel free to send your feedback and support requests by creating dedicated topics in this community.

You can download the new version from our website here. We look forward to your continued input to help enhance our software.

Thank you for your participation in beta testing!