Page MenuHomeFreeBSD

rpcsec_tls/client: API refactoring between kernel and rpc.tlsclntd(8)
ClosedPublic

Authored by glebius on Mon, Jan 20, 9:06 PM.
Tags
None
Referenced Files
F109159921: D48564.diff
Sat, Feb 1, 2:33 PM
Unknown Object (File)
Fri, Jan 31, 5:17 AM
Unknown Object (File)
Sun, Jan 26, 7:39 PM
Unknown Object (File)
Sun, Jan 26, 4:23 AM
Unknown Object (File)
Sat, Jan 25, 8:39 AM
Unknown Object (File)
Thu, Jan 23, 9:10 PM
Unknown Object (File)
Wed, Jan 22, 12:42 PM
Unknown Object (File)
Wed, Jan 22, 8:48 AM
Subscribers

Details

Summary

Now that the conversion of rpcsec_tls/client + rpc.tlsclntd(8) to the
netlink(4) socket as RPC transport started using kernel socket pointer as
a reliable cookie, we can shave off quite a lot of complexity. We will
utilize the same kernel-generated cookie in all RPCs. And the need for
the daemon generated cookie in the form of timestamp+sequence vanishes.

In the clnt_vc.c we no longer need to store the userland cookie, but we
still need to observe the TLS life cycle of the client. We observe
RPCTLS_INHANDSHAKE state, that lives for a short time when the socket had
already been fetched by the daemon with the syscall, but the RPC call is
still waiting for the reply from daemon.

This time bump the RPC version.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable