==========================================================================
The checksum's (found through sum -r) of the files that you have received
(other than this README) are as follows:

29249    359 patchSG0005059.eoe_sw
40035      6 patchSG0005059.eoe_man
35357      4 patchSG0005059
59650      2 patchSG0005059.idb
==========================================================================



				  - 1 -



       1.  Patch_SG0005059_Release_Note

       This release note describes patch SG0005059 for IRIX
       releases	6.5.16m, 6.5.17m, 6.5.18m and 6.5.19m.

       1.1  Supported_Hardware_Platforms

       This patch contains bug fixes for all IRIX platforms.


       1.2  Supported_Software_Platforms

       This patch contains bug fixes for xfsdump on a system
       running IRIX 6.5.16m, 6.5.17m, 6.5.18m or 6.5.19m.  The
       software	cannot be installed on other configurations.

       1.3  Bugs_Fixed_by_Patch_SG0005059

       This patch contains fixes for the following bugs	in IRIX
       6.5.16m,	6.5.17m, 6.5.18m and 6.5.19m.  Bug numbers from
       Silicon Graphics	bug tracking system are	included for
       reference.

	Patch 5059:
	    Fixes:

	      o	Bug #885222 - Security flaw in xfsdump handling	of
		dumped quotafiles

		When xfsdump is	issued on a filesystem with quotas
		enabled, xfsdump calls an external program,
		/usr/etc/repquota, to keep track of the	quotas
		during the dump.  xfsdump calls	repquota with the
		-e flag, which writes all quota	information to an
		output file in a format	that /usr/etc/edquota can
		read back in during the	restore.  The output file
		that is	created	by repquota is unsafe for two
		reasons:

		1) It assumes that the root directory of the
		filesystem is not writable by non-root users.  This
		may not	always be the case.  Any user with write
		privileges to the root directory of a quota-enabled
		filesystem may overwrite any file on the system
		with root privileges (by simply	creating a symlink
		from the quota inventory file(s), xfsdump_quotas
		and/or xfsdump_quotas_group, pointing to any
		file(s)	they wish to destroy.

		2) The file is created with whatever umask xfsdump
		is run as, usually 022.	 This umask allows any user











				  - 2 -



		on the system to view the quota	information of any
		other user, for	the duration of	the filesystem dump
		(since the xfsdump_quotas* files are created with
		mode 644, -rw-r--r--).

       1.4  Subsystems_Included_in_Patch_SG0005059

       This patch release includes these subsystems:

	  o patchSG0005059.eoe_man.base

	  o patchSG0005059.eoe_sw.base

	  o patchSG0005059.eoe_sw.quotas


       1.5  Installation_Instructions

       Because you want	to install only	the patches for	problems
       you have	encountered, patch software is not installed by
       default.	 After reading the descriptions	of the bugs fixed
       in this patch (see Section 1.3),	determine the patches that
       meet your specific needs.

       If, after reading Sections 1.1 and 1.2 of these release
       notes, you are unsure whether your hardware and software
       meet the	requirements for installing a particular patch,	run
       inst.  The inst program does not	allow you to install
       patches that are	incompatible with your hardware	or
       software.

       Patch software is installed like	any other Silicon Graphics
       software	product.  Follow the instructions in your Software
       Installation Administrator's Guide to bring up the miniroot
       form of the software installation tools.

       Follow these steps to select a patch for	installation:

	 1.  At	the Inst> prompt, type

	     install patchSGxxxxxxx

	     where xxxxxxx is the patch	number.

	 2.  Initiate the installation sequence. Type

	     Inst> go

	 3.  You may find that two patches have	been marked as
	     incompatible.  (The installation tools reject an
	     installation request if an	incompatibility	is











				  - 3 -



	     detected.)	 If this occurs, you must deselect one of
	     the patches.

	     Inst> keep	patchSGxxxxxxx

	     where xxxxxxx is the patch	number.

	 4.  After completing the installation process,	exit the
	     inst program by typing

	     Inst> quit



       1.6  Patch_Removal_Instructions

       To remove a patch, use the versions remove command as you
       would for any other software subsystem.	The removal process
       reinstates the original version of software unless you have
       specifically removed the	patch history from your	system.

       versions	remove patchSGxxxxxxx

       where xxxxxxx is	the patch number.

       To keep a patch but increase your disk space, use the
       versions	removehist command to remove the patch history.

       versions	removehist patchSGxxxxxxx

       where xxxxxxx is	the patch number.

       1.7  Known_Problems