---
Now soju accepts PROXY only on specified unix sockets.

Below are some testing commands that i used.

Example soju configuration
...
listen unix:///tmp/sojuaccept.socket
listen unix:///tmp/soju.socket
accept-proxy-from unix:///tmp/sojuaccept.socket
...

Quick testing
[message trimmed]

I had the same issues when using viu with kitty.
What i ended up using is this long filter:

image/*=kitty +kitten icat --stdin=yes --silent --transfer-mode stream --hold --place=120x120@0x7 && kitty +kitten icat --silent --transfer-mode stream --clear

I know that it looks awful, but its good enough for a quick view i guess.
Now icat waits for a key press before exiting and then it clears the image.
Also i had to reposition the image after the top headers and before the
statusline, otherwise the UI becomes a little messy.

On Thu Oct 13, 2022 at 6:02 PM EEST, Simon Ser wrote:
> Hm, I'm a bit worried about users setting up a Unix socket with a
> reverse proxy which doesn't grok PROXY. This would allow clients to
> send arbitrary PROXY headers.

You're right, i hadn't thought about that. What is the simplest way to
make this configurable? Should i add a special case for
"accept-proxy-ip unix"? Or add a new option like "accept-proxy-socket"?

---
Usually we use unix sockets behind reverse proxies on local machines. It
makes sense to trust the proxy protocol we it is available.

Minimal nginx config
..
stream {
	server {
		listen 6697;
		proxy_pass unix:/run/soju/bouncer.socket;
		proxy_protocol on;
	}
}
..
[message trimmed]