[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-17 Thread Phoul
This bug has been revived in the latest hardy update -- /proc/$pid/* gets too restrictive permissions for g-s-t tools https://bugs.launchpad.net/bugs/181088 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing

[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-17 Thread Emilio Pozuelo Monfort
Martin, it seems like you enabled that patch again: - debian/patches/02_noptrace.patch: Disable ptrace() for polkit-gnome-manager, to make it harder to silently abuse gained PK privileges. (See policykit-integration spec). Forwarded to FD#13742. ** Changed in: policykit (Ubuntu)

[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-17 Thread Martin Pitt
I deliberately added the patch again since with 0.7 g-s-t works fine for me with the ptrace protection enabled. What exactly broke for you? ** Changed in: policykit (Ubuntu) Status: Triaged = Incomplete -- /proc/$pid/* gets too restrictive permissions for g-s-t tools

[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-17 Thread Martin Pitt
Let's discuss this in bug 183673. I believe that this bug is fixed. ** Changed in: policykit (Ubuntu) Status: Incomplete = Fix Released -- /proc/$pid/* gets too restrictive permissions for g-s-t tools https://bugs.launchpad.net/bugs/181088 You received this bug notification because you

[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-08 Thread Martin Pitt
I confirm the /proc/pid/exe readlink failure. It doesn't work for g-s-t tools, but I can do it for other processes of mine. I didn't upgrade PK to 0.7 yet because it does not work at all at least for me (tested with gnome-mount). Apparently the dbus API changed and the client apps need updates as

[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-08 Thread Sebastien Bacher
** Changed in: gnome-system-tools (Ubuntu) Target: ubuntu-8.04 = hardy-alpha-3 -- /proc/$pid/* gets too restrictive permissions for g-s-t tools https://bugs.launchpad.net/bugs/181088 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for

[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-08 Thread Martin Pitt
** Changed in: policykit (Ubuntu) Sourcepackagename: gnome-system-tools = policykit Assignee: Ubuntu Desktop Bugs (desktop-bugs) = Martin Pitt (pitti) Status: Confirmed = In Progress Target: hardy-alpha-3 = ubuntu-8.04 -- /proc/$pid/* gets too restrictive permissions for g-s-t

[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-08 Thread Launchpad Bug Tracker
This bug was fixed in the package policykit - 0.6-1ubuntu4 --- policykit (0.6-1ubuntu4) hardy; urgency=low * Disable 02_noptrace.patch for now, since disabling ptrace() also disables reading /proc/pid/exe and PK 0.6 depends on this. (LP: #181088) -- Martin Pitt [EMAIL

[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-08 Thread Saïvann Carignan
Tested latest hardy updates and changing root account with GST now works, thanks for your great work! -- /proc/$pid/* gets too restrictive permissions for g-s-t tools https://bugs.launchpad.net/bugs/181088 You received this bug notification because you are a member of Ubuntu Bugs, which is the

[Bug 181088] Re: /proc/$pid/* gets too restrictive permissions for g-s-t tools

2008-01-07 Thread Sebastien Bacher
Thank you for the detail bug report, I've subscribed Martin who might know about the issue ** Changed in: gnome-system-tools (Ubuntu) Importance: Undecided = High Assignee: (unassigned) = Ubuntu Desktop Bugs (desktop-bugs) Status: New = Confirmed Target: None = ubuntu-8.04