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 1oySqX-0001u6-Ra for pgsql-admin@arkaria.postgresql.org; Fri, 25 Nov 2022 07:10:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oySqW-0004ZQ-Pw for pgsql-admin@arkaria.postgresql.org; Fri, 25 Nov 2022 07:10:00 +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 1oySqW-0004Su-AF for pgsql-admin@lists.postgresql.org; Fri, 25 Nov 2022 07:10:00 +0000 Received: from mail-wr1-x431.google.com ([2a00:1450:4864:20::431]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1oySqS-0001SC-WE for pgsql-admin@lists.postgresql.org; Fri, 25 Nov 2022 07:09:59 +0000 Received: by mail-wr1-x431.google.com with SMTP id s5so5442088wru.1 for ; Thu, 24 Nov 2022 23:09:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=5HWwTauF6a3+lr0aGRUC4uUkTwheFkTmdEcmvCII2XY=; b=1vqLMmINUcCg+cjtrZIAEwVK24eVGsS/pnAedfgUVNo3kRl97ss/Va6TQyMcxb4l33 rvoX5VaobOhwyQJxBhQnEmQsVcxPjIORSSGdfNiAiqpj6e6HfGkeLaC6LAIW3sJt4kOg HkQEYmS8OGvc2th3qAJf9IrDSNvjlVleTKdwGuk/x/kGXlNv6x9Y8Yi9x/E5cSnYmXNO TigQsYKVZms6roBCKPPnIS5i3zff5VebhL9ZI7AIp70O+NGqzxOAPlO075Air7fbyANr PaaiHOyYsXI7fI6TpStQZzAdl+6d2lr+nYhVZE9+tzvqs8FqcTlRo+mneKya82mVCq4b XKsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:user-agent:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=5HWwTauF6a3+lr0aGRUC4uUkTwheFkTmdEcmvCII2XY=; b=px5zNdy+OxUB+bi+9lQWy6Cx+zhH/6WAU78euSiYvNFZZG48PypLKQvya0tkGuD+o4 WyRyfio/ERET5gzK6cpm9TbdrD2GosAJOBu004K0KVxBO15M8BUqCYdXGoviVkjq/xBk 45NUB49Kg43DBfqSrzrvGWdbtwnfIh99rFo9tV3D1zUMIi6N6hw5I+vmiDFJKPzke7wS ncHq03uAYfIB089+LaFJ4eze/hldguHXxBmFTXV3g2Nz8tFQ6fXF+d27rKuJca3h4UZW HPirpm7c+Jp5qv0cFcSx4DGHkeSPbu7TIpUl0hm0PfpjbNsZ+rCFevNYJ1QUPQF6fkZy 6kOw== X-Gm-Message-State: ANoB5pkqCXS0eAnFvkxUDak+ELa2SH6TAMfyCg0wfHZdRpUqVmu0IyAq 0tEFLGIygk9ZZ2HHKjaO+6OOSrTsmINpWg== X-Google-Smtp-Source: AA0mqf4XvNtyPYujM5OLSulFq/5P+NWu+ckPXq6IJPvhfvohqFcbqIwMf+sAasQgI2Pg5Hwxv2+DRw== X-Received: by 2002:a05:6000:1c0e:b0:241:e4d1:d192 with SMTP id ba14-20020a0560001c0e00b00241e4d1d192mr9469797wrb.534.1669360194861; Thu, 24 Nov 2022 23:09:54 -0800 (PST) Received: from localhost.localdomain (mobiledyn-62-240-134-189.mrsn.at. [62.240.134.189]) by smtp.gmail.com with ESMTPSA id bd9-20020a05600c1f0900b003c6bd12ac27sm4268447wmb.37.2022.11.24.23.09.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 24 Nov 2022 23:09:54 -0800 (PST) Message-ID: Subject: Re: Difference between host, hostssl and hostnossl connection type From: Laurenz Albe To: Dhirendra Singh , pgsql-admin@lists.postgresql.org Date: Fri, 25 Nov 2022 08:09:52 +0100 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) 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 Fri, 2022-11-25 at 10:51 +0530, Dhirendra Singh wrote: > I am using postgres version 14. > I would like to know what is the difference between host, hostssl and hostnossl connection type. > According to documentation, > host => This record matches connection attempts made using TCP/IP. host records match SSL or non-SSL > connection attempts as well as GSSAPI encrypted or non-GSSAPI encrypted connection > attempts. > hostssl => This record matches connection attempts made using TCP/IP, but only when the connection > is made with SSL encryption. > hostnossl => This record type has the opposite behavior of hostssl; it only matches connection > attempts made over TCP/IP that do not use SSL. > > I provided cert authentication method for host type connection. but i get error and postgres > does not come up. Following is the error message i get. > LOG: cert authentication is only supported on hostssl connections. "cert" authentication is authentication with SSL (TLS) certificates. You cannot use that authentication without SSL. That is why you have to use "hostssl". Yours, Laurenz Albe