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.98.2) (envelope-from ) id 1x937m-00000001iIT-3OCN for pgsql-bugs@arkaria.postgresql.org; Tue, 22 Sep 2026 16:13:43 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x937m-0000000HLxP-0X8v for pgsql-bugs@arkaria.postgresql.org; Tue, 22 Sep 2026 16:13:42 +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.98.2) (envelope-from ) id 1x8pHr-0000000CQXK-3qvL for pgsql-bugs@lists.postgresql.org; Tue, 22 Sep 2026 01:27:11 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x8pHn-00000000cJE-0Kmt for pgsql-bugs@lists.postgresql.org; Tue, 22 Sep 2026 01:27:11 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=7WCTyQjJUoqjczcqwAZy1JRGrxELn/VuPeUsttKRVA0=; b=T8YXuEg9wkvRTDUF6mYcbARlWm FKB1c6WCefsbbpo4eFryw0AFMI2PGtALOjcXkQjH/RjOKIyRgzzTkXtAZ5ScJYf1o/4lEr5gZClzZ NqAkLBfZbc5h/M38R3/xnkgUkF1gqpcGDxtltsq9sYhkcVqaAL//YYYAI1oefLM4VKiOp0oqpPSvM WH0iQLg5WtQwHEn9AMGrBtqvPmkaZv3PtQKoVjuOd69yNLkbPQFrl4IongU2VDrNU8vImmeBOt/He NP28wS/8rSkjZ2OJDZ67+NKv+UgdXLo1dg5eM8OlFSTVbLl7WqlaLvkUwhBoopTrktH8AJp+VvfFH gQGLFLRA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x8pHl-001pN7-1w for pgsql-bugs@lists.postgresql.org; Tue, 22 Sep 2026 01:27:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x8pHj-00000004rIe-0ke0 for pgsql-bugs@lists.postgresql.org; Tue, 22 Sep 2026 01:27:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19711: SSH tunnel with PPK identity file fails/crashes in newer pgAdmin version but works in older version To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: ayoubcherfaoui19.25@gmail.com Reply-To: ayoubcherfaoui19.25@gmail.com, pgsql-bugs@lists.postgresql.org Date: Tue, 22 Sep 2026 01:26:24 +0000 Message-ID: <19711-ba992e3a50a3fe0f@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19711 Logged by: Ayoub Cherfaoui Email address: ayoubcherfaoui19.25@gmail.com PostgreSQL version: 19beta3 Operating system: Windows Description: =20 I am experiencing an issue when connecting to a remote PostgreSQL server through an SSH tunnel using a PuTTY .ppk private key. With the newer pgAdmin version, the SSH connection fails and I encountered the error Exception: access violation writing 0x0000000000000000. I also received an SSH authentication message indicating that no password or public key was available when using the identity file. I verified that the SSH server is reachable and that the private key is valid. After switching back to an older version, the same server configuration and private key work correctly. This suggests the problem may be related to SSH/PPK private-key handling in the newer version. Environment: Windows 11, pgAdmin 4, SSH tunnel using a .ppk identity file, public-key authentication. The issue is reproducible with the newer version but not with the older version.