Google Is Bringing Chrome Remote Desktop App To Android
An anonymous reader writes "Google is building a Chrome remote desktop app, which lets you access other computers or another user access your computer over the Internet, for Android. The new addition, called Chromoting, will likely be pushed as a mobile version of the existing Chrome Remote Desktop offering. For those who don't know, the original Chrome Remote Desktop is an extension for Google's browser. It was first released as a beta in October 2011 and could be used to control another one of your own computers as well as a friend's or family member's (usually to help with IT issues)."
I feel dirty using Chrome. It's made by Google and I just assume they are snooping on me. For this reason I stick to Firefox even though Chrome is probably faster.
Google may provide a group policy option to disable the chromoting function.... But who is to say an attacker or misbehaving user doesn't later find a bug to turn it back on or circumvent the disablement?
I would have gone with Chroaming personally.
Client-side Javascript is already a security disaster because the unvetted JS code bypasses your perimeter defenses (firewall and proxies) and executes deep inside your privacy domain. And it's not only unvetted code but also unvettable, because it changes with every page.
15 years ago, everyone knew that only the clueless download untrusted 3rd party executable code and run it. Now with JS, all that sensible security advice has been forgotten, and everyone is required to behave clueless with their security. (Software sandboxes are no solution, because all non-trivial software like JS and the browser is riddled with bugs, this is inescapable with large software systems.) Add-ons like NoScript and Ghostery help control it a little, but technically unaware people can't be expected to use them, and more and more websites don't work at all without JS.
And now, Google wants to make it especially easy for remote 3rd parties to access other people's desktops, as if JS didn't make it easy enough already (just ask any security pen-tester). It adds to the already hopeless security in Android, where users are disallowed from blocking the wide access typically demanded by an app on installation. Google doesn't want you to be in control.
The whole Google scene is a security disaster by design. It beats me how a company with so many PhDs can be so cavalier with people's security and hostile to their privacy.
"The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
Am I the only one who's gone from 'oooo, that's cool!' to 'I'm not sure I feel comfortable with that' with a lot of new technology from 'the big guys' recently?
Google own my life. And by extension, my Government, other Governments, security agencies, and many corporate interests own my life.
I've known this forever (and tried not to think about it too much), but with recent disclosures, it's really brought it all home.
All tech I look at now I'm finally asking "So... what data does that give you access to?". It's taking time to figure out a migration path for all my current solutions, but I'm slowly trying to find a route where I'm in control of my data. I know that this probably makes me an idiot, and those that were always privacy concious can laugh - but meh, it's better late than never to come to this realization that I can't trust any third party. Isn't it?
Please avoid using anything from Google. I have considerably reduced my usage of gmail, google drive, and my android tablet. Also, I have decided not to purchase any android-based phone or for that matter any phone from MS, Apple etc.
These companies cannot be trusted. Please DO NOT give them additional access to your computer, phone etc. They already know too much.
...got a bunch of neckbeards bitching about privacy. You don't have any, even if Google wanted to give it to you, the US government made sure of that. Stop blaming fucking Google.
Google really thinks I'm going to give a security sieve like Android mobile (or any phone for that matter) RPC/RDP permissions of any kind? Knowing that an Android can be "rooted" by Google, the carrier, a mildy capable script kiddy,or the government at any time?
Fat fucking chance. The air wall between my phone and my desk stays up.
Scruting the inscrutable for over 50 years.
How about "no and fuck you"?
I'll stick with using VNC from my tablets, laptops, PCs and everything else.
My modded, ripped to pieces (in software terms) tablet at that.
Actually, the lack of a decent Xserver is what makes Androids so totally unusable to me - but I suppose, since it could be useful, that that's not what they are up to.
send + more == money?
Google watching your stuff as 'payment' for their services is not the same as the government watching you, as payment for being a citizen.
One is a choice.
---- Booth was a patriot ----
You would think that Google's stuff would be first available on their own platform...
---- Booth was a patriot ----
I run x11vnc on my Linux desktop and connect remote using androidVNC. Neither are likely to phone home to Google.
Sorry in advance if I missed some crucial piece of information relating to this in the last few weeks.
At what point exactly did we determine that Google was giving ANY information to the NSA of their own accord? (ignoring DMCAs and the like, as I don't think that's the NSAs job).
The whole point of PRISM is that it splits the light signal from fibre optic cables on the internet backbone, which is NOT under Google's control.
As far as we know, when Google announced it had never heard of PRISM before, when it first went public, they could have been telling the truth, as Google would theoretically have no way if telling if something like this was happening outside of their jurisdiction.
This already exists (and works perfectly, I've used it). Why does google feel the need to re-create it? Or are they simply just buying out the company who already created it? https://chrome.google.com/webstore/detail/chrome-remote-desktop/gbchcmhmhahfdphkhkmpfmihenigjmpp?hl=en
... when the websites fail to display correctly on Chrome.
Chrome may be fast (in microseconds) .... but it sucks at displaying MOST websites right.
Here is what we can learn from Google's FAQ
The machine you remote connect on shall accept inbound UDP traffic, and TCP 443 (HTTP/SSL) and 5222 (XMPP, aka Jabber). Google claim to secure the thing using SSL, which suggests your machine will get a x509 certificate signed by Google. But what Common Name will it have? If it is the IP or DNS name, how Google is going to avoid clashes for machines on dynamic IP?
Here is the answer for PRISM interception:
While your connection setup is mediated by Google's servers, your actual remote desktop session data are sent directly from the client to the host, except in limited circumstances where they may pass through Google relays.