3 ms·
If browser and server are on the same machine, you remove a whole host of the barriers to identification. You could use any sort of local knowledge like system
by tootie 8y ago
If browser and server are on the same machine, you remove a whole host of the barriers to identification. You could use any sort of local knowledge like system files or your NIC as identification. NB: I haven't thought this through, but I'm sure there's something to it :)
- jclulow 8y agoOr a system call to identify the process or user on the remote end of a connection; e.g., http://illumos.org/man/3C/getpeerucred http://illumos.org/man/3C/getpeerucred
- adamfisk 8y agoYup that’s the type of thing we do with Lantern. In particular we: 1) Bind to a random port 2) Require a securely random base path for all requests. Anything without that path is rejected. The backend just opens the browser at the random port and base path.