NIS maps value length increase to 16m

From: Konstantin Belousov <kostikbel_at_gmail.com>
Date: Tue, 6 Aug 2019 10:00:22 +0300
Apparently, NIS is still in use even in large enterprise environments,
not everything was consumed by LDAP.  And there, Linux added a quirk
very long time ago, in 2013 at least, see
https://marc.info/?l=fedora-extras-commits&m=136675043230000&w=2

What they did is the increase of the longest allowed key value (and
key name) in a map, from Sun-defined 1024 to 16M.  This change is
backward-compatible, in the sense that either old NIS master or old
NIS client are protocol-compatible with the updated masters and
clients, assuming that the maps only export values limited to 1024
bytes in length.  On the other hand, a new client can use much larger
values.  This works because values are specified in yp XDR as opaque
variadic-length arrays.

An example where this is useful is the environment with very large
automount maps exported by NIS.  For obvious reasons, FreeBSD cannot
function in such settings.

I wrote the patch to bump the limit in FreeBSD NIS implementation,
both in client and in servers, see
https://reviews.freebsd.org/D20900
If you are interested in the NIS code, please review.  I want to commit
the change into HEAD in approximately two weeks from now.
Received on Tue Aug 06 2019 - 05:00:32 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:21 UTC