Authentication-Results: mail-b.sr.ht; dkim=pass header.d=emersion.fr header.i=@emersion.fr
Received: from mail-4317.proton.ch (mail-4317.proton.ch [185.70.43.17])
	by mail-b.sr.ht (Postfix) with ESMTPS id 2A39911EF24
	for <~emersion/soju-dev@lists.sr.ht>; Mon, 24 Oct 2022 13:41:55 +0000 (UTC)
Date: Mon, 24 Oct 2022 13:41:47 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=emersion.fr;
	s=protonmail3; t=1666618913; x=1666878113;
	bh=O9+8QckfSULOhZpWeuNDjfxIT+Z50aIi8T/wSxr/w/s=;
	h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References:
	 Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID:
	 Message-ID:BIMI-Selector;
	b=jOhdcltnfcgy+60AZsB7bShgAv28JsBGkweWgQ5lI5jNioVWsb+ndYy592Q9xw+Bi
	 ztoleLrN3THCnatoXHuzlOqfS93P3YwFX6EpuQByFHS1q9xQzH+4evYvL4WlVVdqAC
	 SY8pDBfBtUPrkk8urGwc3U/Krkz4SK57gxpHVYja+hSladDm0CUEEsd2GoA1nsgggG
	 k+nUkD/oVYuQNfUU2SWRetVEmPoUXRlgduxxQSZ28h5ky+L3xoIqcpxb5Nr57lLBnA
	 cMWgXVcOyuazCUftm6+caEWGdVL6B+JP3XDIZ6qNwdU6cNBZlUDEv7u+vThDGoYDu3
	 oxy8zrh46vrwQ==
To: Julio B <julio.bacel@gmail.com>
From: Simon Ser <contact@emersion.fr>
Cc: ~emersion/soju-dev@lists.sr.ht
Subject: Re: [PATCH v2] Accept proxy protocol on unix sockets
Message-ID: <vFHpP9tUQXGhOu3rSjxElzmHk8q4-JsPRpR9mbFkeJ-riMkZbn-mux2YTALvF3zje9Rsgs2UmQjCBjavlZJoylGJ2vNUsvN-X_q6wKyRNUM=@emersion.fr>
In-Reply-To: <20221019084751.48995-1-julio.bacel@gmail.com>
References: <20221019084751.48995-1-julio.bacel@gmail.com>
Feedback-ID: 1358184:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hm, I'd prefer not to add the filtering based on Unix socket names.
The socket name is not a source address like an IP address is, it's a
destination address. If we were to add it, I think accepting a block
in listen directives would be better:

    listen unix://=E2=80=A6 {
        accept-proxy-from unix
    }

But I'd rather not add it before someone comes with a use-case for it.