Description of feature:
Many server software from WWW server to SQL server support UNIX socket.
I want prosody to support it, so I can use something like this in prosody configuration file.
listen = unix:/run/prosodychat.sock
port = 0 <--- ignored because listen is unix:
Potential usage:
Tor Hidden service ===> unix socket ===> prosody
Zash
on
This is something we want.
Previous discussions have been mostly focused around the Telnet console and low-level networking code.
Being able to restrict the Telnet console using file permissions would be great.
The code that manages all network connections in Prosody, net.server, is currently fairly focused on TCP connections. We want to improve that to ease use of other socket types, like UDP and UNIX sockets.
Changes
tags Status-Accepted
Daniel
on
Will there be a update? It is really stupid that I have to manually specify every IPv6 address in my nginx setup, because I'm proxying Prosody and it is listening at ::1 itself and thus blocking nginx
MattJ
on
@Daniel Can you share more details about your ideal setup in this case?
jSM
on
Hello,
I am also interested in this. I use Nginx streams to proxy communication to Prosody. For now I have Prosody listening on 127.0.0.1, but i would prefer to have it listen on a Unix socket instead.
The rational is security, performance, and the ability to host many Prosody instances without requiring many IP addresses, or weird port mappings.
Boris
on
I would like to try adding unix socket support.
I need it for Syncloud (github.com/syncloud/platform) as part of Jitsi Meet app. Syncloud is a self-hosting platform for not (very) tech people. It allows you to install multiple apps on your device and in this mode having unix socket is super helpful.
My lua/prosody/xmpp experience is zero, but that should not be a problem :)
Any advice is appreciated, from jitsi meet docs I see they use these ports: 5222, 5269, 5347, 5280 so I would concentrate on them.
https://github.com/jitsi/docker-jitsi-meet/blob/master/docker-compose.yml#L186
Description of feature: Many server software from WWW server to SQL server support UNIX socket. I want prosody to support it, so I can use something like this in prosody configuration file. listen = unix:/run/prosodychat.sock port = 0 <--- ignored because listen is unix: Potential usage: Tor Hidden service ===> unix socket ===> prosody
This is something we want. Previous discussions have been mostly focused around the Telnet console and low-level networking code. Being able to restrict the Telnet console using file permissions would be great. The code that manages all network connections in Prosody, net.server, is currently fairly focused on TCP connections. We want to improve that to ease use of other socket types, like UDP and UNIX sockets.
ChangesWill there be a update? It is really stupid that I have to manually specify every IPv6 address in my nginx setup, because I'm proxying Prosody and it is listening at ::1 itself and thus blocking nginx
@Daniel Can you share more details about your ideal setup in this case?
Hello, I am also interested in this. I use Nginx streams to proxy communication to Prosody. For now I have Prosody listening on 127.0.0.1, but i would prefer to have it listen on a Unix socket instead. The rational is security, performance, and the ability to host many Prosody instances without requiring many IP addresses, or weird port mappings.
I would like to try adding unix socket support. I need it for Syncloud (github.com/syncloud/platform) as part of Jitsi Meet app. Syncloud is a self-hosting platform for not (very) tech people. It allows you to install multiple apps on your device and in this mode having unix socket is super helpful. My lua/prosody/xmpp experience is zero, but that should not be a problem :) Any advice is appreciated, from jitsi meet docs I see they use these ports: 5222, 5269, 5347, 5280 so I would concentrate on them. https://github.com/jitsi/docker-jitsi-meet/blob/master/docker-compose.yml#L186