Bug 73989 - [kWnn] Does not work when installed with an umask of 077 and messes filesystem
Summary: [kWnn] Does not work when installed with an umask of 077 and messes filesystem
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: FreeWnn
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: David Lawrence
URL: http://www.tu-chemnitz.de/~ensc/dirch...
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-13 17:06 UTC by Enrico Scholz
Modified: 2007-04-18 16:46 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2003-04-21 11:49:58 UTC


Attachments (Terms of Use)

Description Enrico Scholz 2002-09-13 17:06:46 UTC
Description of Problem:

Because this package contains unowned directories, they will be created
with the current umask. When having restrictive administrator settings
(umask 077) ordinary user will not have access to them and can not use
the package.

Another problem occurs when removing packages. Then orphaned directories
are remaining.

| $ rpm -qf /var/lib/wnn /var/lib/wnn/ko_KR
| file /var/lib/wnn is not owned by any package
| kWnn-1.11-26

IMO this directory should be owned by the FreeWnn-common package which
is required by kWnn.


Version-Release number of selected component (if applicable):

kWnn-1.11-26


How Reproducible:

100%


Steps to Reproduce:
1. umask 077
2. make sure that kWnn is uninstalled completely
   (rm -rf /var/lib/wnn)
3. rpm -U kWnn-1.11-26.i386.rpm
4. ls -l /var/lib/wnn
5. try to use the programs/scripts/libraries/data of the package as
   non-root user
6. rpm -e kWnn-1.11-26

Actual Results:

* at 4:
  | drwx------    2 root     root         4096 Sep 13 18:28 /var/lib/wnn
* files can not be found/read at 5 and
* /var/lib/wnn still exists after 6.

Comment 1 Jens Petersen 2003-04-21 11:49:58 UTC
These days the kWnn subpackage is nolonger being built by FreeWnn.

/var/lib/wnn is owned by FreeWnn at least, which seems good enough
for jserver.


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