From owner-freebsd-current Thu Jun 13 09:08:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA02849 for current-outgoing; Thu, 13 Jun 1996 09:08:13 -0700 (PDT) Received: from expresslane.ca (expresslane.ca [205.233.74.1]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA02843 for ; Thu, 13 Jun 1996 09:08:10 -0700 (PDT) Received: from localhost (james@localhost) by expresslane.ca (8.7.5/8.7.3) with SMTP id MAA05421 for ; Thu, 13 Jun 1996 12:08:08 -0400 (EDT) Date: Thu, 13 Jun 1996 12:08:05 -0400 (EDT) From: James FitzGibbon To: freebsd-current@freebsd.org Subject: UIDs greater than 65535 ? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've noticed a slight discrepancy between the maxmium UID allowed in include/pwd.h, and that allowed in usr.sbin/pw_scan.c. The struct passwd uses : int pw_uid; /* user uid */ But pw_scan.c uses this check routine : if (id > USHRT_MAX) { warnx("%s > max uid value (%d)", p, USHRT_MAX); return (0); } So that although a userid can have a 32-bit value, the password scanning routines won't allow anything higher than 16 bit. Is this just an oversight (i.e. can we just change the constant in pw_scan.c? ) or are there other reasons why the UIDs are limited to 16-bit ? Please reply directly, I'm not on -current for fear of a mail explosion like -stable ... 8-) -- j. +--------------------------------------------------------------------------+ | James FitzGibbon james@expresslane.ca | | Internet Canada Corp. Voice/Fax: 416-363-8518/8713 | +--------------------------------------------------------------------------+