svn commit: r360859 - projects/nfs-over-tls/sys/rpc

[Benjamin Kaduk]

On Tue, May 12, 2020 at 02:32:29PM +0000, Rick Macklem wrote:
> Benjamin Kaduk wrote:
> [stuff snipped]
> >You can avoid having to play games with putting stuff back on the socket
> >receive buffer by using a custom BIO implementation in userspace that knows
> >how to inject the received message.
> >Rick Macklem wrote:
> >>Actually, what might work for the krpc code is a new MSG_TLSAPPDATA
> >>flag for soreceive_generic(), which says "if the record is not application
> >>data, return an error". (Sort of the opposite of what you said above, but
> >>would perform the same thing.)
> >>This could be used for the krpc soreceive() calls, so that the non-application
> >>data record remains on the socket's receive buffer.
> Well, I'd find it a lot easier to implement MSG_TLSAPPDATA, since I've been
> looking at soreceive_generic() recently.
> I'm guessing that a custom BIO would need to be written and the upstreamed
> to openssl?

It doesn't have to be upstreamed; the idea of the API is that it's modular
and anyone can slot in their own implementation for their particular
communication needs.

-Ben