Certificates for localhost

Re:Certificates for localhost by tootie on Wednesday June 20, 2018 @06:28PM (#17360414)

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 :)

[ Parent | on HN ]

Re:Certificates for localhost by jclulow on Wednesday June 20, 2018 @09:30PM (#17361338)

Or a system call to identify the process or user on the remote end of a connection; e.g., http://illumos.org/man/3C/getpeerucred

[ Parent | on HN ]

Re:Certificates for localhost by adamfisk on Wednesday June 20, 2018 @10:53PM (#17361721)

Yup 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.

[ Parent | on HN ]