Page MenuHomeFreeBSD

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

Authored by glebius on Mon, Jan 20, 9:06 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Jan 22, 12:42 PM
Unknown Object (File)
Wed, Jan 22, 8:48 AM
Unknown Object (File)
Wed, Jan 22, 5:56 AM
Unknown Object (File)
Mon, Jan 20, 9:59 PM
Subscribers

Details

Reviewers
rmacklem
Group Reviewers
network
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 Skipped
Unit
Tests Skipped
Build Status
Buildable 61837
Build 58721: arc lint + arc unit