An implementation limit of those lists was introduced in commit
a0ffea098d8c5c5b46c6bf86a12d28d6e7096685 to prevent using unlimited
amounts of memory in ptserver and the client. Subsequent reports
indicate that the chosen limits are small enough to restrict
functionality currently in use at some sites where membership lists
exceed the current limit. Since this is just an implementation-
defined limit and can freely change from release to release, increase
the threshold by an order of magnitude to preserve functionality for
existing deployments while still retaining some protection against
attacker-controlled excessive memory allocation.
Change-Id: I857bb3b697909668eb71224b631dfbb7e3c03d3c
Reviewed-on: https://gerrit.openafs.org/13838
Reviewed-by: Michael Meffie <mmeffie@sinenomine.net>
Reviewed-by: Andrew Deason <adeason@sinenomine.net>
Tested-by: Andrew Deason <adeason@sinenomine.net>
Reviewed-by: Benjamin Kaduk <kaduk@mit.edu>
%#define PR_SF_NUSERS (1u<<30) /* " " foreign users " */
/* OpenAFS implementation limit. This limit can be modified in future releases
- * and does not need to match the limis applied by other implementations. */
-const OPENAFS_MAXPRLIST=50000;
+ * and does not need to match the limits applied by other implementations. */
+const OPENAFS_MAXPRLIST=500000;
typedef char prname[PR_MAXNAMELEN];
typedef prname namelist<OPENAFS_MAXPRLIST>;