7 Commits (04bcc0219dc3acf67f27e68decd6dffe97334779)

Author	SHA1	Message	Date
Oleksandr Redko	60a01d044a	Fix typos in doc comments	2024-04-17 12:00:02 -05:00
Jack Christensen	adbb38f298	Do not allow protocol messages larger than ~1GB ... The PostgreSQL server will reject messages greater than ~1 GB anyway. However, worse than that is that a message that is larger than 4 GB could wrap the 32-bit integer message size and be interpreted by the server as multiple messages. This could allow a malicious client to inject arbitrary protocol messages. https://github.com/jackc/pgx/security/advisories/GHSA-mrww-27vc-gghv	2024-03-04 09:09:29 -06:00
jeremy.spriet	1fdd17041a	feat(pgproto3): expose MaxExpectedBodyLen and ActualBodyLen in ExceededMaxBodyLenErr struct	2024-01-12 18:21:07 -06:00
jeremy.spriet	603c8c1e90	feat(pgproto3/backend): add a SetMaxBodyLen to limit the max body length for the receive	2023-12-23 10:25:35 -06:00
Jack Christensen	7f382f5190	Better fuzz testing and fix several bugs it found ... Fix infinite loop in AuthenticationSASL.Decode Fix panic in CommandComplete.Decode Fix panic in DataRow.Decode Fix panic in NotificationResponse.Decode	2022-07-23 16:13:06 -05:00
Jack Christensen	5714896b10	Restructure sending messages ... Use an internal buffer in pgproto3.Frontend and pgproto3.Backend instead of directly writing to the underlying net.Conn. This will allow tracing messages as well as simplify pipeline mode.	2022-05-21 11:06:44 -05:00
Jack Christensen	04476c4a13	Move pgproto3 to subdirectory	2022-02-21 11:57:34 -06:00