| From: | Vaishnavi Prabakaran <vaishnaviprabakaran(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Error-like LOG when connecting with SSL for password authentication |
| Date: | 2017-05-23 02:11:23 |
| Message-ID: | CAOoUkxTgj-URMnPvopzSC4mNYKn0GThhrbJAE=62wE9pSnyRQg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 22, 2017 at 5:10 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:
> If the protocol version is SSL
> 3.0 or TLS 1.0, this result code is returned only if a closure alert
> has occurred in the protocol, i.e. if the connection has been closed
> cleanly. Note that in this case SSL_ERROR_ZERO_RETURN does not
> necessarily indicate that the underlying transport has been closed.
>
I guess this error code exist even for SSL2 protocol, In that case, don't
we need to keep the current code for this error code?
Regards,
Vaishnavi,
Fujitsu Australia.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-05-23 04:55:48 | Re: psql - add special variable to reflect the last query status |
| Previous Message | Michael Paquier | 2017-05-23 01:47:18 | Re: Some thoughts about SCRAM implementation |