Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ptvcn-0002I0-Lt for pgsql-general@arkaria.postgresql.org; Tue, 02 May 2023 19:25:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ptvcm-0000AT-GL for pgsql-general@arkaria.postgresql.org; Tue, 02 May 2023 19:25:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ptvcm-0000AI-68 for pgsql-general@lists.postgresql.org; Tue, 02 May 2023 19:25:20 +0000 Received: from mail-pl1-x62f.google.com ([2607:f8b0:4864:20::62f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ptvcj-000Aud-I8 for pgsql-general@lists.postgresql.org; Tue, 02 May 2023 19:25:18 +0000 Received: by mail-pl1-x62f.google.com with SMTP id d9443c01a7336-1aaec6f189cso22492135ad.3 for ; Tue, 02 May 2023 12:25:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683055516; x=1685647516; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=ILTt/nx8nYxP6PyomtcAkN7wpImHwdLoEUb2wh49Pwc=; b=e84JM7pcwRIl//U4PR8/vzvYTKdxG9+EF5Kwp7nUuVxxgKFrkzreSvBdmfDubLfOFw G39RE7LdXbLjqcVtqQ+J8sLTfGkwm88/x5X1KXONTX8MCIgGTF0hS7YqM+ILqQhKwPO5 c3YThl37XZKrbhYC3wjMI0goYCjY8nOvjW3ph4w/sJCq7a8rBAeIn/V4wFrT2+qa5LCL Si6pbDsF7wTrLXHdRpI+KG45ybO6T7g7mVzxCPF2WeUyAg8YfFQ+nl7JO8MnijO57Dd5 gbNpPdM4CBbvQs8BlOI+QGlffcRUNXRXaWiDSaKP01aZlXZQ8IyIJk9CCFp49psIw8Z+ tV6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683055516; x=1685647516; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ILTt/nx8nYxP6PyomtcAkN7wpImHwdLoEUb2wh49Pwc=; b=EcBSqrUi4mDzYGGqLtZS7ZEsYPZjK7JpLqVQ6wfvr0YbGCt1/YDCCZ/DheP7gug52/ iVYttZVLMzonS8tVrSMeMQeWyYXI/t5TkSnHpnRy85thmyPCwCkt1E66bGhiS0dByETi 713LjFwO8rn2Ln0axMoo0TC+/7MNtcIpUp15J/Qhvgv7cv30vPwQ4+f4ZNdhBUj0Tb7N 6Fl1n8P3TVOyQRePy42zljY9KnDG5B+tfqHHn3GiwZ7alv2ZrnuOQzTzXEg5TFENBaLa 9JxO1CZgWOK3KIKugGNxGwC9ULXLdpMU86rG9J2pizcgTMzdd8yt+TA2A+/TDF+64eYo zPHA== X-Gm-Message-State: AC+VfDwkXTVKmWVy8TeHO6GpZ2oSDogkLU1hIMbcotuI8Af8le7elGca G7DFHQLZt+dgppOAmZ1QUdcvcZiYOoE= X-Google-Smtp-Source: ACHHUZ6VTiEQm022e1fIe7gjz1PYdspPbg37YFa+DGRBFrteQw3bCLn3iVz2bwQ17U5z63iJsq8C4g== X-Received: by 2002:a17:902:e5c2:b0:1ab:c04:362e with SMTP id u2-20020a170902e5c200b001ab0c04362emr3868780plf.52.1683055515869; Tue, 02 May 2023 12:25:15 -0700 (PDT) Received: from ?IPV6:2601:681:5a00:f790:e50b:73:5f78:fee5? ([2601:681:5a00:f790:e50b:73:5f78:fee5]) by smtp.gmail.com with ESMTPSA id cf17-20020a17090aebd100b0022be36be19asm1731814pjb.53.2023.05.02.12.25.14 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 02 May 2023 12:25:15 -0700 (PDT) Message-ID: <08bd7e3f-5af8-d380-6ee6-4cacc5d0ac46@gmail.com> Date: Tue, 2 May 2023 13:25:13 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: Regarding SSL Enablement in PostgreSQL Database on different port Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: From: Rob Sargent In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/2/23 13:15, Tomas Pospisek wrote: > > Oh, I think your idea to use pgbouncer to take care of the SSL > termination is elegant. I don't think me I'd characterize it as a hack > if properly set up. Why do you consider it a hack? > *t > > > Let me guess:  postgres IS NOT listening on the other port, pgbouncer is with it's own users and mappings and protocol setup and then sending what ever's  encrypted to the actual port postgres  is listening on which could have been used directly (with maybe on less cert?) I use pgbouncer btw.  For balance.