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

unix domain socket #15

Closed
whyrusleeping opened this issue Nov 15, 2015 · 5 comments
Closed

unix domain socket #15

whyrusleeping opened this issue Nov 15, 2015 · 5 comments

Comments

@whyrusleeping
Copy link
Member

would be neat if we could have multiaddrs to represent unix domain sockets

@jbenet
Copy link
Member

jbenet commented Nov 17, 2015

yes would be nice.

/uds/path/to/sock
or
/unix/path/to/sock

?

hard to tell --then-- when a uds addr ends without looking into the fs. opens up the door for certain attacks. It may be useful --then-- to constrain the actual sock file (the last component member of uds to always say .uds or .sock or something. this is already typical, but making it required would save us headaches.

@ghost
Copy link

ghost commented Mar 18, 2019

We already have /unix

@ghost ghost closed this as completed Mar 18, 2019
@infinity0
Copy link

@lgierth how does one escape the slashes in a typical filepath?

/unix/home/tcp/80/no/wait/my/username/really/is/tcp/honest/tcp/80?

@Stebalien
Copy link
Member

One does not. Unfortunately, /unix is currently a terminal path. That is, everything after /unix is a path.

There are a bunch of discussions (e.g. multiformats/multiaddr#63) in the mutliaddr repo trying to figure this out.

@infinity0
Copy link

Ah, thanks for the pointer.

Stebalien pushed a commit that referenced this issue May 20, 2020
make multiaddr-net more pluggable
This issue was closed.
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

4 participants