[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#765499: Patch to make policy document 32-bit uids



On Sat, Jan 31, 2015 at 12:28:22PM -0800, Russ Allbery wrote:
> Bill Allombert <ballombe@debian.org> writes:
> 
> > +	      <tag>4294967294:</tag>
> > +	      <item>
> > +		<p>
> > +		  <tt>(uid_t)(-2) == (gid_t)(-2)</tt> <em>must
> > +		  not</em> be used, because it is mistaken for
> > +                  <tt>65534</tt> <prgn>nobody</prgn> by some
> > +                  programs.
> > +		</p>
> > +	      </item>
> 
> I would instead say:
> 
>     <em>must not</em> be used, because it is used as the anonymous,
>     unauthenticated user by some NFS implementations.

OK I offer an updated patch.

Third time's a charm I hope.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here. 
diff --git a/policy.sgml b/policy.sgml
index 24cf7d7..947a1e1 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7351,6 +7351,35 @@ rmdir /usr/local/share/emacs 2>/dev/null || true
 	      <tag>65535:</tag>
 	      <item>
 		<p>
+		  This value <em>must not</em> be used, because it was
+		  the error return sentinel value when <tt>uid_t</tt>
+		  was 16 bits.
+		</p>
+	      </item>
+
+	      <tag>65536-4294967293:</tag>
+	      <item>
+		<p>
+		  Dynamically allocated user accounts.  By
+		  default <prgn>adduser</prgn> will not allocate UIDs
+		  and GIDs in this range, to ease compatibility with
+		  legacy systems where <tt>uid_t</tt> is still 16
+		  bits.
+	        </p>
+	      </item>
+
+	      <tag>4294967294:</tag>
+	      <item>
+		<p>
+                  <tt>(uid_t)(-2) == (gid_t)(-2)</tt> <em>must not</em> be
+                  used, because it is used as the anonymous, unauthenticated
+                  user by some NFS implementations.
+		</p>
+	      </item>
+
+	      <tag>4294967295:</tag>
+	      <item>
+		<p>
 		  <tt>(uid_t)(-1) == (gid_t)(-1)</tt> <em>must
 		  not</em> be used, because it is the error return
 		  sentinel value.

Reply to: