| Summary: | dconf can not access to /run/user/1000/dconf/user | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Atilla ÖNTAŞ <tarakbumba> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | critical | ||
| Priority: | Normal | CC: | ankiesaini147, mageia, nic |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: |
this patch forces root to use its own homedir (.config/dconf)
Reviewed dconfsu patch |
||
|
Description
Atilla ÖNTAŞ
2013-11-11 14:44:47 CET
The patch only solves one of the side effects of this problem, but really the consequences go far, far deeper than dconf - e.g. run mc and see root owned files in your home dir. I would actually argue that this patch is broken as it changes XDG usage behaviour for one particular user. For this reason I expect Matthias to reject the patch in dconf and thus we'd have to carry it as a downstream. As this is just papering over the cracks of the problem rather than solving it, I'd personally rather not include it, but my vote is certainly not final in that regard. Pragmatism may dictate it's better to include it until some better design can come along. The fundamental fact remains however, that using something like su to run GUI apps (or even any apps that use sufficiently high level libs) is just a broken concept by design. All su does is change the uid. It's basically a wrapper around a ioctl and nothing will change that fact. A modern desktop is just not designed to run tools like that as root and the more we can do to discourage users from doing this the better. IMO our efforts would be better spent making it as awkward as possible (or even totally impossible) to use su in this way. Again that's just my opinion. I'll watch the RH bug and see what Matthias' reaction is. CC:
(none) =>
mageia (In reply to Colin Guthrie from comment #1) You' re compeletly right. Because of this i called this patch as workaround not a fix. But we need to fix or workaround this issue before Mageia 4 release. I think until a fix issued we should use this patch to avoid this bug. Created attachment 4514 [details]
Reviewed dconfsu patch
While i'm not a programmer/coder i tried to revise the dconfsu patch to not leaky. I hope i made things right.
Attachment 4500 is obsolete:
0 =>
1 Hi!
As mentioned on the list, this is a step in the right direction :)
Two main points:
1. the outer if statement should have { } surrounding the inner one (this is not a bug but it aids clarity of reading - especially if indentation were to change).
2. "if (getuid != 0)" should be "if (getuid() != 0)" otherwise the patch has no effect and doesn't solve anything :)
Good work so far tho'. Keep it up!
(In reply to Colin Guthrie from comment #4) Thank you Colin, i have modified the patch as suggested and committed to both Cauldron and Mga3/Updates. Requested push. For now i think this bug report should remain open, while we workaround the bug there is no real fix. Until it is fixed in su or pam... Colin, do you have any progress on this? We still use patched dconf... It is almost 2 years since last comment. Is the issue fixed? CC:
(none) =>
nic
Samuel Verschelde
2016-10-16 15:28:22 CEST
Assignee:
bugsquad =>
pkg-bugs We still use patched dconf but main issue seems fixed.But not a clean and nice way. Anyways, closing this bug report. Status:
NEW =>
RESOLVED
ankit saini
2019-04-04 12:04:00 CEST
CC:
(none) =>
ankiesaini147 |