>Number:         6447
>Category:       misc
>Synopsis:       supped files are world writable
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    misc-bug-people (Misc Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sun Nov 15 08:05:01 1998
>Last-Modified:
>Originator:     Jim Bernard
>Organization:
	Speaking for myself
>Release:        November 15, 1998
>Environment:
System: NetBSD zoo 1.3H NetBSD 1.3H (ZOO) #0: Sun Oct 18 08:48:41 MDT 1998 local@zoo:/home/local/netbsd-current/usr/src/sys/arch/i386/compile/ZOO i386


>Description:
	For at least most of this month, sup has been setting world-writable
	permission on all newly retrieved files.  This seems like a rather
	bad idea, since we have no protection against this (e.g., we can't
	simply specify a umask for sup to use) other than to run find & chmod
	on the local tree after every sup.

>How-To-Repeat:
	cd /usr/src; ls -lgR

>Fix:
	I assume this reflects permissions on the file server--the fix is
	obvious.
>Audit-Trail:
>Unformatted: