Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s1Wlo-00CvFi-GK for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Apr 2024 19:34:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s1Wll-001oHS-LE for pgsql-hackers@arkaria.postgresql.org; Mon, 29 Apr 2024 19:34:34 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s1Wll-001oEr-BJ for pgsql-hackers@lists.postgresql.org; Mon, 29 Apr 2024 19:34:34 +0000 Received: from mail-qv1-xf33.google.com ([2607:f8b0:4864:20::f33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s1Wli-000eXq-Vp for pgsql-hackers@lists.postgresql.org; Mon, 29 Apr 2024 19:34:32 +0000 Received: by mail-qv1-xf33.google.com with SMTP id 6a1803df08f44-69b6c2e9ed9so22895896d6.1 for ; Mon, 29 Apr 2024 12:34:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1714419270; x=1715024070; darn=lists.postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=AMbss2jUN9uZXXFuFo0BV4JqxcZnjuKdK+ExRth8uok=; b=SF57iBzEjgCn108kpLfvlsHPZwgFErx535L1BzMjvrYawYGL75/nBsRPNUUrCnUikO Rf7DhkXsWAAFvH4CQKtKRgqSASp9Hk/CIHAJep2ic2yT+7MVT4ov7XIQ9GCb7zWCqM+4 rlHh8e4wfxNYDoc5Pefb/y528V9XiPaTcYCoNgAJHi8p1kBrt23mfU1kLYZLDzelK7as 6Jp+fl4o/O2WZkLU5qrhli/9V7Eyk8VUo7etbDYFC7uSpXT7NtiCMRMzWop5gLAus3UX YUP5nQOP1ZVlgHOb4c7XRjv7DUhmYtfCbvxNT4Yifnnaf2e/3Yhvp/eQ/ir6IoyWHAYo NuTg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714419270; x=1715024070; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=AMbss2jUN9uZXXFuFo0BV4JqxcZnjuKdK+ExRth8uok=; b=rURYim4O539xq30CClonaRS37rEY75RGBFWx5egCMZjV8JrGOEKry0Y9fg75ZIjPG9 dJDBCmru/p6TkqDaUkOcrWifQwCU776wgIStPjMjPZaPWtqpK66kTZo/y8QCBrBHSsfH dF6BIg5C7ReNYGydLcta/8yI/gjM30zUkuLs7M/jW36rvdla3dVoSLmFOtCsNb5bbiuG 3emZp7c8ztu5E8dtjZYnHNY7fNfLZsAq6HNF/8mtC1NsXzzTJmE0Syes7LNsR/+ehKIz 8eqgffCPkRwbMblGcxQ7cEPwhq5NwvMzCDPH/pld1gP12MxISB5C1dOkgg6poojRawXh AVIA== X-Forwarded-Encrypted: i=1; AJvYcCUoA+4ysORDqz+BwDaSI+Yuxz/2mQcE+MfBii8MKNjaBg+GvX0LMzFl0jgXadtPByznJERvUCjfbIJ3rYtm0bnePG/0S3/dJvXZlUsJAEqcwXmg X-Gm-Message-State: AOJu0YwxltgeN/twCPIIi4KFasFJjE7U9TlDY3Qdq0jLQy/ISk9LLuSm ofoqq1f6iGr6XtH4TMwIjJcX0dD/5q5DTwF/psBQ7HNlEKamDVmknSjR10emowGyzzHXnpQEsju RJP7VKu/qwkaafU1Wck3AUW/AGpHg3AimSZgo X-Google-Smtp-Source: AGHT+IH+4AZajQXZupcyYPZMq1m45eNlhMlETiDr7aIHQGh3CdDt7aZl51ffRysAko6BJZC6odCthrbZamvALa3Xqx0= X-Received: by 2002:ad4:5cae:0:b0:6a0:cd5f:d8d1 with SMTP id q14-20020ad45cae000000b006a0cd5fd8d1mr5268478qvh.50.1714419269856; Mon, 29 Apr 2024 12:34:29 -0700 (PDT) MIME-Version: 1.0 References: <5a79ed71-b365-4b20-80bc-9c2bf97bf84b@iki.fi> <3a6f126c-e1aa-4dcc-9252-9868308f6cf0@iki.fi> <1a717f65-7390-4111-8efd-c6e9b213805e@iki.fi> In-Reply-To: From: Jacob Champion Date: Mon, 29 Apr 2024 12:34:18 -0700 Message-ID: Subject: Re: Direct SSL connection with ALPN and HBA rules To: Heikki Linnakangas Cc: Daniel Gustafsson , Robert Haas , Michael Paquier , Postgres hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Apr 29, 2024 at 12:32=E2=80=AFPM Jacob Champion wrote: > > On Mon, Apr 29, 2024 at 12:06=E2=80=AFPM Heikki Linnakangas wrote: > > On 29/04/2024 21:43, Jacob Champion wrote: > > > But if you're in that situation, what does the use of directonly give > > > you over `sslnegotiation=3Ddirect`? You already know that servers > > > support direct, so there's no additional performance penalty from the > > > less strict mode. > > > > Well, by that argument we don't need requiredirect/directonly at all. > > This goes back to whether it's a security feature or a performance feat= ure. > > That's what I've been trying to argue, yeah. If it's not a security > feature... why's it there? Er, I should clarify this. I _want_ requiredirect. I just want it to be a security feature. --Jacob