Bug 12150 - msec weekly reports 2000+ lines of world writable file found in /var/tmp/systemd-private-xxxxx
Summary: msec weekly reports 2000+ lines of world writable file found in /var/tmp/syst...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Colin Guthrie
QA Contact:
URL:
Whiteboard:
Keywords: Junior_job
Depends on:
Blocks:
 
Reported: 2013-12-30 00:27 CET by Thomas Spuhler
Modified: 2015-10-27 06:58 CET (History)
1 user (show)

See Also:
Source RPM: msec
CVE:
Status comment:


Attachments

Description Thomas Spuhler 2013-12-30 00:27:17 CET
Description of problem:
msec weekly reports about 2000+ lines of security issues. All files look like this
 /var/tmp/systemd-private-ZZuQeF

Version-Release number of selected component (if applicable):
systemd-195-22.1.mga3

How reproducible:
Ever sunday

Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Thierry Vignaud 2013-12-30 05:32:41 CET

CC: (none) => thierry.vignaud
Assignee: bugsquad => mageia

Comment 1 Thomas Spuhler 2015-01-10 17:53:37 CET
any news on this Colin?
Comment 2 David Walser 2015-03-08 17:23:18 CET
These are just PrivateTmp directories.  systemd is doing exactly what it's supposed to.

The bug is in msec.  It shouldn't include directories with the sticky bit in its "world-writeable" report.

Source RPM: systemd => msec

Comment 3 Marja Van Waes 2015-03-31 16:05:38 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD

Comment 4 Thomas Spuhler 2015-03-31 16:14:21 CEST
Still valid in mga4

Status: RESOLVED => REOPENED
Version: 3 => 4
Resolution: OLD => (none)

Thierry Vignaud 2015-04-01 09:16:34 CEST

Keywords: (none) => Junior_job

Comment 5 Samuel Verschelde 2015-09-21 13:21:07 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 6 Marja Van Waes 2015-10-27 06:58:13 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: REOPENED => RESOLVED
Resolution: (none) => OLD


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