X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 54AA69DCA8C for ; Sun, 26 Mar 2006 11:58:20 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 35227-01 for ; Sun, 26 Mar 2006 11:58:24 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from smtp.nildram.co.uk (smtp.nildram.co.uk [195.112.4.54]) by postgresql.org (Postfix) with ESMTP id E21309DC981 for ; Sun, 26 Mar 2006 11:58:17 -0400 (AST) Received: from demolish1 (unknown [84.12.162.61]) by smtp.nildram.co.uk (Postfix) with SMTP id 5C53A335A70 for ; Sun, 26 Mar 2006 16:58:18 +0100 (BST) Message-ID: <001201c650ee$1b1901a0$0264a8c0@demolish1> From: "Donald Fraser" To: "[ADMIN]" Subject: Initial request packet for SSL Date: Sun, 26 Mar 2006 16:58:20 +0100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000F_01C650F6.7C7B9A90" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.127 required=5 tests=[AWL=0.126, HTML_MESSAGE=0.001] X-Spam-Score: 0.127 X-Spam-Level: X-Archive-Number: 200603/271 X-Sequence-Number: 21028 This is a multi-part message in MIME format. ------=_NextPart_000_000F_01C650F6.7C7B9A90 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hello, I'm not sure whether this is the correct place to post this question, = but I will try here first. According to the documentation, to connect to the back-end using SSL a = special start-up packet (SSLRequest) is required before the front-end = can begin with the SSL hand-shake. My question is, can this initial request be avoided in any way - is it = possible to start with the SSL handshake without the request? The reason I'm asking is that I've been asked to write some software = that will establish a secure connection through a HTTPS proxy server to = a PostgreSQL database. My research shows that to tunnel through a proxy = requires first the connection to the proxy server and then the SSL = hand-shake. Many HTTPS proxy servers will not allow any data to be = transmitted before the SSL hand-shake, which in the case for PostgreSQL = is going to cause problems if I'm required to send the SSLRequest packet = first. Any thoughts would be appreciated, regards Donald Fraser.=20 ------=_NextPart_000_000F_01C650F6.7C7B9A90 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hello,
I'm not sure whether this is the correct place to = post this=20 question, but I will try here first.
 
According to the documentation, to connect to=20 the back-end using SSL a special start-up packet (SSLRequest) is = required=20 before the front-end can begin with the SSL = hand-shake.
 
My question is, can this initial request = be avoided in=20 any way - is it possible to start with the SSL handshake without the=20 request?
 
The reason I'm asking is that I've been asked to = write some=20 software that will establish a secure connection through a HTTPS proxy = server to=20 a PostgreSQL database. My research shows that to tunnel through a proxy = requires=20 first the connection to the proxy server and then the SSL hand-shake. = Many HTTPS=20 proxy servers will not allow any data to be transmitted before the SSL=20 hand-shake, which in the case for PostgreSQL is going to cause problems = if I'm=20 required to send the SSLRequest packet first.
 
Any thoughts would be appreciated,
regards
Donald Fraser. 
 
 
------=_NextPart_000_000F_01C650F6.7C7B9A90--