From: | Magnus Hagander <mha(at)sollentuna(dot)net> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | RE: [HACKERS] Re: SSL patch |
Date: | 1999-07-24 17:38:37 |
Message-ID: | 215896B6B5E1CF11BC5600805FFEA82101F70B72@sirius.edu.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > As it is right now, it should work in all combinations except a 6.6
client
> > compiled with SSL support connecting to a pre-6.6 server. It already
> > falls-back if the server is 6.6 (without SSL support). And the 6.6
client
> > compiled without SSL works.
>
> Actually, it shouldn't matter whether the server is 6.6-without-SSL
> or pre-6.6. At least in the way I envisioned it, they'd act the same.
Not quite.
The 6.6-without-SSL still knows about the NEGOTIATE_SSL_CODE packet that is
sent, and can respond "No, I can't do SSL". The pre-6.6 does not know about
the existance of this packet, and will thus respond with "Unsupported
Frontend Protocol" (since it's a normal StartupPacket with the version
number set to something very large (like the cancel request was
implemented)).
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-07-24 17:50:21 | Re: [HACKERS] RE: [INTERFACES] Re: SSL patch |
Previous Message | Oleg Bartunov | 1999-07-24 17:23:20 | Re: [HACKERS] Re: [SQL] inserts/updates problem under stressing ! |