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 1lUn9L-0004FX-Ue for pgsql-admin@arkaria.postgresql.org; Fri, 09 Apr 2021 09:09:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lUn9J-0003oi-95 for pgsql-admin@arkaria.postgresql.org; Fri, 09 Apr 2021 09:09:57 +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 1lUn9J-0003oV-1F for pgsql-admin@lists.postgresql.org; Fri, 09 Apr 2021 09:09:57 +0000 Received: from mail-ed1-x536.google.com ([2a00:1450:4864:20::536]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lUn9C-0006So-S0 for pgsql-admin@postgresql.org; Fri, 09 Apr 2021 09:09:56 +0000 Received: by mail-ed1-x536.google.com with SMTP id ba6so5695240edb.1 for ; Fri, 09 Apr 2021 02:09:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:cc:date:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=zYrusdqDTf1dnI8xTuNbpe671Y5bq0ER51wdbsEPWoE=; b=a+EEi/CblL8/zdbS10AZUHWzEb6kwdRB3PpLZMWu+SzodmcYJt/OT4DdeI/gYt9CSR z1kTUlP/wdUIgwagoPMCnmX6NMguYM7GeehCjkHQT+GCaoL8S2De6WHAt9+HE6ayzetz buVu+8K/Z0V52Iso6Eo5tCXg9+m4vMpru3Ohu4s5KG7cWk92uTNcPMU09g05MV7nWfsF bxNS+pXRpJIv2uDlA7rz1PiGVj+0QGFxzpGSsCNlyMenTsv5Q7V3XmOfbD5rdM0Qdd3s SqITQg2wyXjUd3EgMDLvG4wnk9LwhrP2zF+fi1xwZ3LHSSzv8ocjGwG02Ejd3kog+IaJ R3RQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=zYrusdqDTf1dnI8xTuNbpe671Y5bq0ER51wdbsEPWoE=; b=G6FRWzRR3tRK4d0/sb1SvJieo133Z5PgQC2RNah3dZLHhj8ng/KLpfXJ7ae9t0gDlx M6c3/oFr75M8TDRiLVzQXgrsm0hylvOkbsVwhPI52qOaF2JE0wwglK+8msbLavqAAsnO 3NiyKoZFi5SImRbjk1QlgigSCJ3Q2raX92jRQOham5ciLIw1GEE9OJ2swiXQMIFSPetf 08yW1ykQjMBrYLbJ82Jh9Nv92Tb789LEFjN312zQEoX016Pwa31GR0DDebiwG07AbTp1 5jOaksUBvF+ZEEVACLvtXJbhz93zR7hx+VQp/i2tpIHaQbCLsehTBG0TAGqSaVR5AwFs BJoA== X-Gm-Message-State: AOAM531isHc4wVPZtQTVv0lGt3giNs7xtlMWIHkEJDvc9Ss6KNZM664u NwA+5rWKkreHkpASO/hCKHhZOgb8v5AgKw== X-Google-Smtp-Source: ABdhPJxn7zniDTb5kZ6rNgQx3PoqG4sv3ywCJmEBXQJErb/eUrGMQqzRbawqy5TrtcMch1Pe0mlbgg== X-Received: by 2002:aa7:cb90:: with SMTP id r16mr16875292edt.139.1617959388117; Fri, 09 Apr 2021 02:09:48 -0700 (PDT) Received: from localhost.localdomain (217-149-171-143.nat.highway.telekom.at. [217.149.171.143]) by smtp.gmail.com with ESMTPSA id ca1sm1051210edb.76.2021.04.09.02.09.47 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 09 Apr 2021 02:09:47 -0700 (PDT) Message-ID: <749e43831c8fd197fa06560746c9ff4d474ac2dd.camel@cybertec.at> Subject: Re: Replication & TLS encryption - how? From: Laurenz Albe To: lejeczek Cc: pgsql-admin@postgresql.org Date: Fri, 09 Apr 2021 11:09:46 +0200 In-Reply-To: <9d29a3c7-80de-4408-9197-e5ce1dd54a8e@yahoo.co.uk> References: <54a5bf2b-0504-02c0-e5a2-ab24173abcdb.ref@yahoo.co.uk> <54a5bf2b-0504-02c0-e5a2-ab24173abcdb@yahoo.co.uk> <1596782.1617813374@sss.pgh.pa.us> <7e89a9be-e788-23fc-6b1b-2ee67586d452@yahoo.co.uk> <84304703ff2131cb3302eaf12b31a235b25a76a6.camel@cybertec.at> <9d29a3c7-80de-4408-9197-e5ce1dd54a8e@yahoo.co.uk> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2021-04-08 at 12:37 +0100, lejeczek wrote: > I get what you were saying but I also wondered - when I > showed my "primary_conninfo" & pg_hba: why does replication > appear to work without the bits you mention and what is the > significance of 'clientcert=1' in all this. Replication works just fine when unencrypted. "clientcert=1" (in versions before v12) means that the server will reject a client connection unless it sends a client certificate that is signed by an authority that the server recognizes. If you omit the option (or set it to 0), the server doesn't care if the client sends a certificate or not. Note that by default, PostgreSQL uses SSL only to encrypt the connection, not to verify the identity of the participants.