Yuli Khodorkovskiy 1c20e7d36e Fix malformed SASL messages
Per the PG documentation [0], an AuthenticationSASLContinue message has:

    AuthenticationSASLContinue (B)
	Byte1('R')
	    Identifies the message as an authentication request.
	Int32
	    Length of message contents in bytes, including self.
	Int32(11)
	    Specifies that this message contains a SASL challenge.
	Byten
	    SASL data, specific to the SASL mechanism being used.

The current implementation was mistakenly adding the lengh of msg bytes
in between the Int32(11) and Byten. There was a similar issue for
AuthenticationSASLFinal.

[0] https://www.postgresql.org/docs/current/protocol-message-formats.html
2019-12-17 20:28:01 -05:00
2019-03-30 12:33:04 -05:00
2017-04-29 10:02:38 -05:00
2019-08-31 11:53:26 -05:00
2019-06-08 19:38:34 -05:00
2019-06-08 19:38:34 -05:00
2019-06-08 19:38:34 -05:00
2019-08-31 11:53:26 -05:00
2019-08-31 11:53:26 -05:00
2019-03-30 12:32:39 -05:00
2019-06-08 19:38:34 -05:00
2017-05-26 17:00:44 -05:00
2019-09-07 11:37:43 -05:00
2019-08-31 11:53:26 -05:00
2019-08-31 11:53:26 -05:00

Build Status

pgproto3

Package pgproto3 is a encoder and decoder of the PostgreSQL wire protocol version 3.

pgproto3 can be used as a foundation for PostgreSQL drivers, proxies, mock servers, load balancers and more.

See example/pgfortune for a playful example of a fake PostgreSQL server.

Extracted from original implementation in https://github.com/jackc/pgx.

Description
PostgreSQL driver and toolkit for Go
Readme MIT 7.6 MiB
Languages
Go 98.6%
HTML 1.2%
Shell 0.2%