3 ms·

Yes basically it's two browsers talking to each other. But there is an important thing to notice. You need to run a signaling server running somewhere. You can

Yes basically it's two browsers talking to each other. But there is an important thing to notice. You need to run a signaling server running somewhere. You cant run a signaling server in browser. When doing screen sharing between two browsers it basically goes to external signaling server on internet and asks credentials and then doing peer to peer communication. Deskreen can run without access to world wide web with its own local signaling server. The speed is also much better when doing direct communication through local signaling server running on host machine. Hope that helps you to understand it better. Cheers

Animats 6y ago
Deskreen can run without access to world wide web with its own local signaling server. That should be the standard setup. Allowing any access to your screen via a remote server is a huge security hole.
- kevincox 6y ago
  A signaling server does not provide access to your screen. The clients can verify that they are connected to each other without MITM.
kevincox 6y ago
I can see the benefit of a local signaling server however I am always online so I would be happy to run it in my browser and avoid running electron. > The speed is also much better when doing direct communication through local signaling server running on host machine. This should only affect the setup time right? As soon as the connect is established the signaling server should not be required.
- pavlobu 6y ago
  Not quite. As I've tested the speed is much slower when I'm using a simple-peer API with external IPC servers array filled in. You may use what better fits your use case. But I want to mention that I made and end-to-end encryption for initial signals to be sent to each other. Signals are basically encrypted and hard to hack. Also deskreen has a lot of alrets and confirmations so you can always check your devices IPs. Also it has Lock Room feature -> meaning as soon as someone connected to a socket, it is immediately locked and no one can access it except 2 host and client devices. But you can have a look in source code and maybe find some security leaks. Please submit the issue if you find it. By the way I forgot to reference simple peer on github, let me fix that soon.

Animats 6y ago

Deskreen can run without access to world wide web with its own local signaling server. That should be the standard setup. Allowing any access to your screen via a remote server is a huge security hole.

kevincox 6y ago
A signaling server does not provide access to your screen. The clients can verify that they are connected to each other without MITM.

kevincox 6y ago

I can see the benefit of a local signaling server however I am always online so I would be happy to run it in my browser and avoid running electron. > The speed is also much better when doing direct communication through local signaling server running on host machine. This should only affect the setup time right? As soon as the connect is established the signaling server should not be required.

pavlobu 6y ago
Not quite. As I've tested the speed is much slower when I'm using a simple-peer API with external IPC servers array filled in. You may use what better fits your use case. But I want to mention that I made and end-to-end encryption for initial signals to be sent to each other. Signals are basically encrypted and hard to hack. Also deskreen has a lot of alrets and confirmations so you can always check your devices IPs. Also it has Lock Room feature -> meaning as soon as someone connected to a socket, it is immediately locked and no one can access it except 2 host and client devices. But you can have a look in source code and maybe find some security leaks. Please submit the issue if you find it. By the way I forgot to reference simple peer on github, let me fix that soon.