Chrome RDP

[America]

I haven't worked helpdesk for 3 years loser. I'm a deployment engineering specialist, level III. And I have forgot more about Internet Protocol than your $50,000 debt ever learned you. Your pride will cost this man his job if he listens to you.

Go read the documentation and copy paste how I'm wrong. You won't. Because you can't.

[this user was banned]

Originally Posted by America [You must be logged in to view images. Log in or Register.]

Chrome RDP doesn't work like other incantations of RDP. It runs virtual applications, cloned from RAM of the viewed PC, locally on the viewer machine and superimposes them over cropped jpgs or png or whatever sent from the viewed PC. That way the images transferred can be much smaller, and bandwidth constraints are much less an issue. It's a wild implementation. Side effects, of course, Google gets to read the state of the applications and track user behavior thoroughly for advertising. And the traffic can be read by IP log and deep package inspection as though the remote machine were local. Check out the docs, chrome rdp is wackadoodle af.

Ok, but isn't the only socket connection to EQ being run on the home PC's hardware? You can't trace that from RDP if the physical machine has no connection to his work PC other than through the HTTPs based RDP connection.

Or does Chrome use your local PC's hardware for networking instead of the home PC?

If you started EQ on the home PC then connected to it and picked it up at work, the process and socket are only running on the home PC, otherwise EQ will just not work because it would need to open a new connection on new hardware. Maybe there's something I'm missing?

[branamil]

How about you copy and paste the part from the documentation where it "clones ram"?

[misterbonkers]

Originally Posted by this user was banned [You must be logged in to view images. Log in or Register.]

Ok, but isn't the only socket connection to EQ being run on the home PC's hardware? You can't trace that from RDP if the physical machine has no connection to his work PC other than through the HTTPs based RDP connection.

Or does Chrome use your local PC's hardware for networking instead of the home PC?

If you started EQ on the home PC then connected to it and picked it up at work, the process and socket are only running on the home PC, otherwise EQ will just not work because it would need to open a new connection on new hardware. Maybe there's something I'm missing?

p99 client will stop working when rdp starts so you'd have to start it after getting in

[America]

Originally Posted by branamil [You must be logged in to view images. Log in or Register.]

How about you copy and paste the part from the documentation where it "clones ram"?

You're the one giving reckless advice. Maybe the onus is on you.

Originally Posted by this user was banned [You must be logged in to view images. Log in or Register.]

Ok, but isn't the only socket connection to EQ being run on the home PC's hardware? You can't trace that from RDP if the physical machine has no connection to his work PC other than through the HTTPs based RDP connection.

Or does Chrome use your local PC's hardware for networking instead of the home PC?

If you started EQ on the home PC then connected to it and picked it up at work, the process and socket are only running on the home PC, otherwise EQ will just not work because it would need to open a new connection on new hardware. Maybe there's something I'm missing?

The EQ instance is cloned from host (or whatever, the viewed machine I mean) to client (viewer) and run locally. Then a bitwise two-way synchronization is done as the application state changes.

It's bizarre. That's why it takes so long to "buffer", though, and why achievable framerate is so high. Check the docs out, it's wild.

[Wonkie]

this the extra chrome zone thread

[this user was banned]

Originally Posted by America [You must be logged in to view images. Log in or Register.]

The EQ instance is cloned from host (or whatever, the viewed machine I mean) to client (viewer) and run locally. Then a bitwise two-way synchronization is done as the application state changes.

It's bizarre. That's why it takes so long to "buffer", though, and why achievable framerate is so high. Check the docs out, it's wild.

Ok, but the ACTUAL TCP connection to EQ is only run through the hardware on the home PC; I'm not sure that network traffic between the home PC and the EQ servers would ever be visible through Chrome RDP.

The network traffic for EQ wouldn't even route through his work PC would it? His work would only be able to monitor his work PC's traffic and they would only see the HTTPS traffic from Chrome RDP.

[America]

Originally Posted by this user was banned [You must be logged in to view images. Log in or Register.]

Ok, but the ACTUAL TCP connection to EQ is only run through the hardware on the home PC; I'm not sure that network traffic between the home PC and the EQ servers would ever be visible through Chrome RDP.

The network traffic for EQ wouldn't even route through his work PC would it? His work would only be able to monitor his work PC's traffic and they would only see the HTTPS traffic from Chrome RDP.

ohhhh that's a good question. I had to look into the doc for this.

Turns out though that it's not safe. While the bitwise sync is active, Chrome RDP protocol designates a "primary incarnation" window based upon the most recent user interaction timestamp and conducts all tcpip from that machine. Weird. p99 might just drop the connection in that case. Check it out:

https://support.google.com/chrome/an...ynchronization

[this user was banned]

Originally Posted by America [You must be logged in to view images. Log in or Register.]

ohhhh that's a good question. I had to look into the doc for this.

Turns out though that it's not safe. While the bitwise sync is active, Chrome RDP protocol designates a "primary incarnation" window based upon the most recent user interaction timestamp and conducts all tcpip from that machine. Weird. p99 might just drop the connection in that case. Check it out:

https://support.google.com/chrome/an...ynchronization

There's nothing in that link about that besides how to set up Chrome RDP for me.

If his work PC is running the tcpip traffic to P99 then he's clearly at risk, but there's a good chance, if his company is smart, they've got all ports on lockdown except maybe HTTP/HTTPS

If work isn't blocking the windows RDP port, they could just use that instead and I believe they would be safe.

[America]

Originally Posted by this user was banned [You must be logged in to view images. Log in or Register.]

There's nothing in that link about that besides how to set up Chrome RDP for me.

hmm, are you logged in to a Google developer account? i think they cost 5 bucks or something. i bought one for extension publishing.