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 1slnef-001H0X-2E for pgsql-general@arkaria.postgresql.org; Wed, 04 Sep 2024 10:54:29 +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 1slned-007yIA-A4 for pgsql-general@arkaria.postgresql.org; Wed, 04 Sep 2024 10:54:27 +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 1slnec-007yI2-Ta for pgsql-general@lists.postgresql.org; Wed, 04 Sep 2024 10:54:27 +0000 Received: from mail-lj1-x22b.google.com ([2a00:1450:4864:20::22b]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1slneb-0006ec-6t for pgsql-general@lists.postgresql.org; Wed, 04 Sep 2024 10:54:26 +0000 Received: by mail-lj1-x22b.google.com with SMTP id 38308e7fff4ca-2f3f163e379so17449681fa.3 for ; Wed, 04 Sep 2024 03:54:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725447263; x=1726052063; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=UB15ijL0Ob/FktpTeTdqP+0XBprrmg/3Gi/tQ2xg1EM=; b=XClJ6EmowSS9gIO0sG2pYpPDc5Y5uH6D7NyEjXaQncKTW6+WnHNy3lLTYVuc8V74WP m2B3L7lnCMpnvqbwlOBvnVKtBLwDJHFNr1JdICG9VXe9vo+PzcRuzGcO+4pfJEWw3itx WcgT5GF1qzf6xI+cRcDqwFxP/R6FyTCqVNwsSW2UnBxAN/GstnrntZLDjDMa4AykrIm6 oELzJzWZieoqu7vVnRac0rv4Gz82J3DmAQ8CrmJqvN1fkCGlRayBvm4ZTNPssMp8o3/L n2xx1VRdjIqS6MGCHiJN4yDgYEDvD+AB5SsnEbGR8BKaSMvJ+Hf2QFTS3bV0TsRXtQuK J6sQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725447263; x=1726052063; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=UB15ijL0Ob/FktpTeTdqP+0XBprrmg/3Gi/tQ2xg1EM=; b=Hn/tTAtxYoherZkCsnG8vTL3WGBex67doKdhoo8GotwJmM/8aB9TLeO7g6yvbJYu4x OHogy0GE4aPlCqPANiktMDpahAN4clBXfdcrmdMWQCAQF3JFctkVhPwapy3LGmyH9I23 FjWKavTijhkJ5LBhjHCobephkQ5yM8KaMeiGxNCz2CxDsFewBD+7gpHuNxIhXG10+k4O Hpr+k9ErSIeBmYwf9Ns0OpUcSni8Jvb1F467xgoGC1LJL1I/xNBlk+RMl40z5FVqmwwl jis1szJiB8NrTUsG0iiWzj7RsCod/htvd3ZyAoskliipUpREekVMWIoukcVjDNLgaNfh 7HeQ== X-Gm-Message-State: AOJu0YwdypufqCM9LsrDx+AC806UkG/ek1i0eEM0PFEioCjAb1EGs4yN gUGijCqp8cCSq9aI0mKrLywsBfXwoAwzrpf3L8atq52UYd+6iog4eLwCmRlXfP7f0uIHetlkit1 OzmsPfN47h7IHD/kGrGpU6Gyat+Vxhuk2 X-Google-Smtp-Source: AGHT+IEzN85NYAj9uwfnqvexpzTZwiUfiY03o2jD7UHWi6p9u/AUfjkNvKZXUl3kMLk7rKn9LxiZku5H9NLMX/c2Vmc= X-Received: by 2002:a2e:4e09:0:b0:2ef:2555:e52d with SMTP id 38308e7fff4ca-2f6108ae923mr139865731fa.45.1725447263415; Wed, 04 Sep 2024 03:54:23 -0700 (PDT) MIME-Version: 1.0 From: MM Date: Wed, 4 Sep 2024 11:54:12 +0100 Message-ID: Subject: libpq15 with postgres server16 and scram-sha-256 To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000036f8d4062148ffae" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000036f8d4062148ffae Content-Type: text/plain; charset="UTF-8" Hello is it possible to connect with PGConnectdb version 15 to a server that has in METHOD in pg_hba.conf "scram-sha-256" or do I need version libpq 16 ? If so, being constrained to remain at 15 libpq for now, is md5 allowed? Rds, --00000000000036f8d4062148ffae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello
is it possible to connect with PGConnectdb versi= on 15 to a server that has in METHOD in pg_hba.conf=C2=A0 =C2=A0"scram= -sha-256"
or do I need version libpq 16 ?

=
If so, being constrained to remain at 15 libpq for now, is md5 a= llowed?

Rds,
--00000000000036f8d4062148ffae--