Magnus Hagander <mha@sollentuna.net> writes:
> Well, I see one reason to change it. Which is why I came up with the
> question in the first place. I was looking at the possibility of putting SSL
> on top of libpq. I have a project I'm working on that needs to transmit
> "lightly sensitive data" across the internet. Right now using SSH
> forwardings, but that's not exactly the "ideal solution".
> Anyway, SSLeay has functions that replace read() and write(), but nothing to
> work with FILE *:s.
> So if there are no major objections, I might take a shot at changing it to
> working directly on the socket, and put SSLeay on it.
Ah. Now that you mention it, I recall someone bringing up that exact
issue last summer on the hackers list. Was that you? If not, you might
want to go digging in the list archives (I forget what was said...)
regards, tom lane
