Bug 200843 - rss-glx: world writable docs
Summary: rss-glx: world writable docs
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rss-glx
Version: 5
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-31 21:27 UTC by Ville Skyttä
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-08-01 12:08:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ville Skyttä 2006-07-31 21:27:42 UTC
3 files in rss-glx's docs (FE5 and devel) are world writable.  See bug
200794 for background and more info.

Comment 1 Nils Philippsen 2006-08-01 12:08:07 UTC
rss-glx-0.8.1.p-5 is building for FC5 and Rawhide. The culprit was just copying
over source files instead of using install so they files inherited my local
(002) umask.

Comment 2 Ville Skyttä 2006-08-01 16:30:41 UTC
Actually your local umask should not affect anything in the buildsys, but this
is most likely an issue with the buildsys having 000 umask when it checks out
stuff to build from CVS.

Comment 3 Nils Philippsen 2006-08-02 14:48:44 UTC
Well, the files were created and checked in with my local umask, CVS tends to
retain these permissions, so they propagated into the build system.


Comment 4 Ville Skyttä 2006-08-02 16:09:14 UTC
CVS remembers only whether the file had executable bits on at initial check in
time and retains that status, everything else is forgotten, and decided by the
checkouter's umask at checkout time.  Besides, your local umask was 002, not 000 ;)

$ umask
0022
$ rm README.fedora ; cvs -Q up README.fedora
$ ls -l README.fedora | cut -d' ' -f 1
-rw-r--r--
$ umask 000
$ umask
0000
$ rm README.fedora ; cvs -Q up README.fedora
$ ls -l README.fedora | cut -d' ' -f 1
-rw-rw-rw-

Comment 5 Nils Philippsen 2006-08-03 11:46:55 UTC
Agreed.



Note You need to log in before you can comment on or make changes to this bug.