Skip to content

Add support for Unix sockets for Web Service and DoH#1753

Open
IngmarStein wants to merge 1 commit intoTechnitiumSoftware:masterfrom
IngmarStein:feature/unix-sockets
Open

Add support for Unix sockets for Web Service and DoH#1753
IngmarStein wants to merge 1 commit intoTechnitiumSoftware:masterfrom
IngmarStein:feature/unix-sockets

Conversation

@IngmarStein
Copy link
Contributor

This adds support for listening on Unix domain sockets in addition to TCP ports for both the Web Service (HTTP/HTTPS) and DNS-over-HTTPS (DoH).

Unix sockets are often used for these reasons:

  • Secure Local IPC: They allow secure, high-performance connections from a local reverse proxy (like Nginx or HAProxy) without exposing the service on local TCP ports, which could be accessible to other local users or processes.
  • Performance: They avoid the overhead of the TCP/IP networking stack (routing, packet encapsulation, etc.), leading to lower latency and higher throughput for proxy setups.
  • Security: Access to Unix sockets can be strictly controlled using standard file system permissions (chown/chmod), providing an additional layer of security over local TCP loopback binding.

The configuration has been updated to support a single Unix socket path for HTTP and HTTPS variants of the Web UI and DoH services.

This adds support for listening on Unix domain sockets in addition to TCP ports
for both the Web Service (HTTP/HTTPS) and DNS-over-HTTPS (DoH).

Unix sockets are often used for these reasons:
- Secure Local IPC: They allow secure, high-performance connections from a
  local reverse proxy (like Nginx or HAProxy) without exposing the service
  on local TCP ports, which could be accessible to other local users or
  processes.
- Performance: They avoid the overhead of the TCP/IP networking stack
  (routing, packet encapsulation, etc.), leading to lower latency and
  higher throughput for proxy setups.
- Security: Access to Unix sockets can be strictly controlled using
  standard file system permissions (chown/chmod), providing an additional
  layer of security over local TCP loopback binding.

The configuration has been updated to support a single Unix socket path
for HTTP and HTTPS variants of the Web UI and DoH services.
@ShreyasZare
Copy link
Member

Thanks for the PR. Will review it soon.

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

Successfully merging this pull request may close these issues.

2 participants