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 1s6vjs-002XNc-RA for pgsql-hackers@arkaria.postgresql.org; Tue, 14 May 2024 17:14:58 +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 1s6vjs-000BL4-OV for pgsql-hackers@arkaria.postgresql.org; Tue, 14 May 2024 17:14:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s6vjs-000BKw-E4 for pgsql-hackers@lists.postgresql.org; Tue, 14 May 2024 17:14:56 +0000 Received: from mail-ot1-x32f.google.com ([2607:f8b0:4864:20::32f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s6vjn-000Dul-GJ for pgsql-hackers@lists.postgresql.org; Tue, 14 May 2024 17:14:54 +0000 Received: by mail-ot1-x32f.google.com with SMTP id 46e09a7af769-6f0fbfc6f80so724990a34.3 for ; Tue, 14 May 2024 10:14:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1715706889; x=1716311689; 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=fKq14YUVFMd1BsAMqWnxXkMk8cRARGK63ePt5BztUwg=; b=IxL+7AmqZa508OopEmW9J1XKifbQNEQKZI3KfEX9FdXNGTy9Jyq3cJfHZCber1gtr3 GRu0x8mPp58biimelM8e8GhV4xB4lwkKElbT+7AYzFdazyLqxVjalw/CTmshbnP4KiTL Z2DkmiAxKNlFmyooyYCbCBOflQbyg4fEHCO3aa9EcydMf7ESC62cwcoqEM8GCg8LBSA9 XRsHdCwxnOyMCXiIaZ7CB3YYcdpjRvLxVcEfLZ7QpcAovs/DVBY5GFNPppu/GXWgZrlu CkauBKI5GkgeWavZ9z16y6BdIAqdIgTzj7x3N20QQ/InIEnj2IqKrZtfpexoCMZagLVh tpMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715706889; x=1716311689; 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=fKq14YUVFMd1BsAMqWnxXkMk8cRARGK63ePt5BztUwg=; b=O0IWJzPqU3TY9DrLWZs1k2nANEYfaOt7q8Lfu32b50OLOQKB06qvIoUUZFuCLXKEui O/3rjyW60aX3pThdVGYqJT3S94iZTzXu0HLowbOiKGpnwLpj50deLreeWOTQ6Ji2ls5Y QUbUUDcUeK7M2LsprfseGRsz0aHseABBwWdzaeWTlBO3YHthzHlMOvMtlh3y67kaqkts E3u7fCZL2wTlRCQcElPZ0Q/O3QRbP1tVZKgmTthUFRypmtGmWzZNTQtTd3S3CkbrQZJJ z+0FYeDPHWwVcDdlfWiZWPvxbSw0QUUdk77+sGhimXBe03lH8rMP2igelkq5TE9Z3c75 AnrA== X-Forwarded-Encrypted: i=1; AJvYcCVWl+X6dIMV6DjJNuiW1p/9vTatpoZhDhqCUvdyM8V1W0ArdYv+ckhv41iEXkcBEUWxuFzWHmihkKGHXeN2LAt5f2SrU0jGKkE35Pkgn92kJ3wO X-Gm-Message-State: AOJu0YwUJncgJNlEatBVK7v1/VYSf1fyqHses397hKofIWVHHnLVNP4y Ol8akKzhSNDm7l+y26dQt9kzl0hZEr2mOtJtZisZ0SF1B6f0LQSlu7GtgRetuOSeM+1oroVb+ff uqdVeeIb6BDI911f0o9iO6xMr/PS8FaVerLB/4M6W4dcS4Hqmjw== X-Google-Smtp-Source: AGHT+IFYk2UiG2yqQRA5FnG/K0o1DhBlrWj3jAPGEzuIMiYFJROWc007hftxP5LGN6IGtceEuFn9XyHByNdk7tRlKYc= X-Received: by 2002:a9d:6301:0:b0:6ef:9594:2c05 with SMTP id 46e09a7af769-6f0e90fb6f4mr14541942a34.1.1715706889556; Tue, 14 May 2024 10:14:49 -0700 (PDT) MIME-Version: 1.0 References: <6aedcaa5-60f3-49af-a857-2c76ba55a1f3@iki.fi> In-Reply-To: From: Jacob Champion Date: Tue, 14 May 2024 10:14:38 -0700 Message-ID: Subject: Re: Direct SSL connection with ALPN and HBA rules To: Heikki Linnakangas Cc: 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 11:04=E2=80=AFAM Jacob Champion wrote: > On Fri, Apr 26, 2024 at 3:51=E2=80=AFPM Heikki Linnakangas wrote: > > Unfortunately the error message you got in the client with that was > > horrible (I modified the server to not accept the 'postgresql' protocol= ): > > > > psql "dbname=3Dpostgres sslmode=3Drequire host=3Dlocalhost" > > psql: error: connection to server at "localhost" (::1), port 5432 > > failed: SSL error: SSL error code 167773280 > > > > I filed a bug upstream [1]. I think this is on track to be fixed in a future set of OpenSSL 3.x releases [2]. We'll still need to carry the workaround while we support 1.1.1. --Jacob [2] https://github.com/openssl/openssl/pull/24351