Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to use local sockets on localhost #31

Open
c42f opened this issue Jan 7, 2022 · 0 comments
Open

Option to use local sockets on localhost #31

c42f opened this issue Jan 7, 2022 · 0 comments

Comments

@c42f
Copy link
Collaborator

c42f commented Jan 7, 2022

It would be nice to have the option to use unix domain sockets or windows named pipes when both client and server are on localhost. This should improve security a lot on unix systems where permission to connect can be defined by local filesystem permissions.

Perhaps this should even become the safe and secure default, with users having to opt into using TCP because it comes with security problems on multi user systems.

IIRC SSH can also open tunnels to socket files, so perhaps we could keep the tunnel-based remote access functionality by default as well. We'd need to figure out an appropriate location for the socket files within the user's home directory, or some such.

See also discussion in #29 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant