Re: libpq compression (part 3)
От | Jacob Champion |
---|---|
Тема | Re: libpq compression (part 3) |
Дата | |
Msg-id | CAOYmi+n6xQcA664DUDn5HsHTrT2u0hebfNYkgzJ=1J7zSOEx4A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: libpq compression (part 3) (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: libpq compression (part 3)
|
Список | pgsql-hackers |
On Mon, May 20, 2024 at 10:01 AM Robert Haas <robertmhaas@gmail.com> wrote: > I really hope that you can't poke big enough holes to kill the feature > entirely, though. Because that sounds sad. Even if there are holes, I don't think the situation's going to be bad enough to tank everything; otherwise no one would be able to use decompression on the Internet. :D And I expect the authors of the newer compression methods to have thought about these things [1]. I hesitate to ask as part of the same email, but what were the plans for compression in combination with transport encryption? (Especially if you plan to compress the authentication exchange, since mixing your LDAP password into the compression context seems like it might be a bad idea if you don't want to leak it.) --Jacob [1] https://datatracker.ietf.org/doc/html/rfc8878#name-security-considerations
В списке pgsql-hackers по дате отправления: