#927: move dump location from /var/spool/abrt to /var/tmp/abrt
--------------------+------------------------------
Reporter: jfilak | Owner: crash-catcher@…
Type: task | Status: new
Priority: major | Milestone:
Component: abrt | Version:
Keywords: | Blocked By:
Blocking: |
--------------------+------------------------------
== Rationale ==
Get rid of directory stealing.
----
== FHS compliance (current state) ==
We have been saving dump directories in '/var/spool/abrt' because we
wanted to
be complaint with FHS (we consider dump directory as a data waiting to be
reported). For good security reasons users are not allowed to add new
files to
dump directory or write into existing dump directory files (e.g. wasting
of all
root FS free space).
'''Implementation'''
- set dump directory uid to abrt's user id because we want to allow abrt
binaries to process dump directories.
- set dir's gid to crashed application's user gid because we want to
remember who experienced the problem.
- (just for the record: we can't set dir's uid to crashed
application's user uid because owner can modify dir's rights).
'''Advantages'''
- great safeness
- arguable FHS compliance
'''Disadvantages'''
- leads to '''stealing of directories''' because events require
write
access to a
dump directory and events are run under non root (abrt) user while
reporting (no write access by default).[[BR]]
''Consequences:''
- broken local duplicate detection (if a problem has been stolen the
second
occurrence is not recognized as duplicate)
- root can't see stolen problems
- and few more difficulties
- group members can see crashes of other group members.
Institutions like schools uses one common group for all students.
----
== Partial FHS compliance (proposal) ==
In order to avoid struggling with FHS compliance disadvantages we grant
users
ownership of dump directories (give them read/write access). But we can't
allow
users to have write acces in '/var/spool/abrt', therefore we have to place
dump
location in '/var/tmp/abrt'
'''Implementation'''
- set dump dir's uid to crashed application's user uid, and we set gid
to
abrt's group id.
- allow write access to group because we want to allow abrt
binaries to process dump directories.
'''Advantages'''
- no Strong Security disadvantages
'''Disadvantages'''
- arguable safeness (?)
- in order to protect file system the dump directories must be saved in
'/var/tmp/abrt'
- arguable FHS compliance
--
Ticket URL: <
https://fedorahosted.org/abrt/ticket/927>
Automatic Bug Reporting Tool - ABRT <
http://fedorahoted.org/abrt/>
Automatic bug reporting tool