Conrad Sallian's community posts

RSA with 2048-bit key.

BTW, we'll soon publish a special document/white paper that gives an in-depth look into and summarizes all security features, protocols and algos used in Remote Utilities.

Hello,

All traffic between Viewer and Host is RSA-encrypted even when you are working via your own self-hosted server anyway.

Hi Michael,

Unfortunately, we can't help with this because apparently this has something to do with the underlying IDE /environment that we to build the Android app. I recommend you waiting till the next update of Android app.

Responded in tickets, thanks.

I should say, that Remote Utilities is not supposed to be used for remote gaming, especially when a certain app (or game) occupies the screen in monopoly mode.

There are better ways to stream video/sound from a game to a different PC. For example, the In-house streaming from Steam.

Hello,

droodle wrote:
Any closer to having a Linux version ??

Sorry, but no. There are a lot of priories in front of us before we consider working on the Linux version. I'm sorry for that.

Hello Michael,

Thank you for your message.

Does restarting the device or re-installing the software from Play store work?

Hello John,

Thank you for the detailed workaround. However, we need to resolve the cause, not the effect :) And we are doing this currently, by contacting Symantec and Google.

Symantec has already responded that they fixed the false positive and the results will take effect within 24 hours.

Thanks, John.

Update on this issue. It seems like the root cause for the Chrome issue is Symantec falsely detecting our program as risky/potentially dangerous. Which in itself is very strange given the fact that our digital certificate is issued by VeriSign and there haven't been any false positive issues with Symantec for very long. We assume that Chrome somehow uses the data from Symantec and aggregates them with data from other vendors, but we are not sure. We have already reported this to Symantec and hopefully the issue will be resolved soon.

It should be noted though that Google Chrome is very quick in going from a mere assumption to a final verdict. That is from the subtle "may harm your browsing experience" to calling the file as being outright malicious.  :D

UPD: sorry, just noticed that you have already provided the instruction in your message. So I've deleted mine :)

You are welcome  :)  Let us know whenever you need any assistance.

Hi Mike,

I'll check with our developers if there is any ETA and get back to you soon.