- 30 Nov, 2018 1 commit
-
-
Ray Strode authored
polkitbackend: Fix some minor typos in an internal comment See merge request polkit/polkit!12
-
- 29 Nov, 2018 1 commit
-
-
Philip Withnall authored
Signed-off-by:
Philip Withnall <withnall@endlessm.com>
-
- 06 Nov, 2018 5 commits
-
-
Ray Strode authored
[l10n] Add Italian translation See merge request polkit/polkit!6
-
Milo Casagrande authored
Signed-off-by:
Milo Casagrande <milo@milo.name>
-
Ray Strode authored
Fix a critical warning on calling polkit_permission_new_sync with no system bus See merge request polkit/polkit!8
-
-
Ray Strode authored
Updated Czech translation See merge request polkit/polkit!7
-
- 25 Sep, 2018 1 commit
-
-
Marek Cernocky authored
-
- 12 Sep, 2018 3 commits
-
-
Ray Strode authored
Update Brazilian Portuguese translation See merge request polkit/polkit!5
-
-
Ray Strode authored
Update Polish translation 180821 See merge request polkit/polkit!1
-
- 23 Aug, 2018 4 commits
-
-
Piotr Drąg authored
-
Jan Rybar authored
Err msgs to debug See merge request polkit/polkit!3
-
Jan Rybar authored
Superuser should know that polkit is not running in emergency.target. If not, basic info with debug sources is offered instead of error message. Other usecases taken into account.
-
Jan Rybar authored
Polkit raises unnecessarily elaborate warning message when user restarts machine from ssh. This message was moved to debug mode.
-
- 16 Aug, 2018 1 commit
-
-
Ray Strode authored
-
- 15 Aug, 2018 1 commit
-
-
Jan Rybar authored
Resolves: bz#106021 Subject: [PATCH] polkitd: fix zombie not reaped when js spawned process timed out The child watch source attached to thread context didn't work due to the release of it's main loop and context outside. So we attach the source to the global default main context to make it work and avoid zombies.
-
- 09 Aug, 2018 1 commit
-
-
Jan Rybar authored
-
- 10 Jul, 2018 1 commit
-
-
Miloslav Trmač authored
-
- 03 Jul, 2018 2 commits
-
-
Miloslav Trmač authored
-
Miloslav Trmač authored
As part of CVE-2013-4288, the D-Bus clients were allowed (and encouraged) to submit the UID of the subject of authorization checks to avoid races against UID changes (notably using executables set-UID to root). However, that also allowed any client to submit an arbitrary UID, and that could be used to bypass "can only ask about / affect the same UID" checks in CheckAuthorization / RegisterAuthenticationAgent / UnregisterAuthenticationAgent. This allowed an attacker: - With CheckAuthorization, to cause the registered authentication agent in victim's session to pop up a dialog, or to determine whether the victim currently has a temporary authorization to perform an operation. (In principle, the attacker can also determine whether JavaScript rules allow the victim process to perform an operation; however, usually rules base their decisions on information determined from the supplied UID, so the attacker usually won't learn anything new.) - With RegisterAuthenticationAgent, to prevent the victim's authentication agent to work (for a specific victim process), or to learn about which operations requiring authorization the victim is attempting. To fix this, expose internal _polkit_unix_process_get_owner() / obsolete polkit_unix_process_get_owner() as a private polkit_unix_process_get_racy_uid__() (being more explicit about the dangers on relying on it), and use it in polkit_backend_session_monitor_get_user_for_subject() to return a boolean indicating whether the subject UID may be caller-chosen. Then, in the permission checks that require the subject to be equal to the caller, fail on caller-chosen UIDs (and continue through the pre-existing code paths which allow root, or root-designated server processes, to ask about arbitrary subjects.) Signed-off-by:
Miloslav Trmač <mitr@redhat.com>
-
- 03 Apr, 2018 19 commits
-
-
Ray Strode authored
The NEWS entry for the 0.114 release says the release was made a year earlier than it was. It's too late to fix the NEWS file in the actual release, but still better to have it correct in version control.
-
Ray Strode authored
commit 00adeee1 attempted to add a "%s" format string to the two JS_Report invocations that needed it, but somehow only got one them. This commit gets the other one. https://bugzilla.gnome.org/show_bug.cgi?id=105865
-
Ray Strode authored
-
Ray Strode authored
-
Ray Strode authored
Currently polkit depends on mozjs24 to provide the JavaScript support for the JavaScript authority. The problem is, mozjs24 is quite old at this point. Most other parts of the desktop have moved on. This patchset updates polkit to target mozjs52, instead. As a side benefit, we can re-enable the JIT, since it no longer seems to conflict with the watchdog thread used to detect when a javascript script is caught in an infinite loop. Most of the porting work was made by looking at what changes GJS performed when it retarted mozjs versions, and mimicing them. I also got some inspiration and a commit from an earlier port to mozjs38: https://lists.freedesktop.org/archives/polkit-devel/2017-April/000533.html
-
Jeremy Linton authored
An implicit authorization parameter is provided to polkit_backend_js_authority_check_authorization_sync() for actions without corresponding explicit rules. Assure that is honored rather than simply being denied. Signed-off-by:
Jeremy Linton <jeremy.linton@arm.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
seems to work with mozjs52 Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
it's not around anymore. Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
JS_EvaluateScript is no longer in the API set, so use JS::Evaluate instead. Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
JS_ExecuteScript no longer takes a global argument. Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
The global object is implicit now and the result is an out arg. This commit adapts to the new api. Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
This commit drops usage of JS_AddObjectRoot and switches the global object over to being wrapped in a JS::Heap pointer. It stops using JS_DefineObject which no longer seems to be available, and adds a new JS::FireOnNewGlobalHook which seems to be required. Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
seems like it got renamed. Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
The way args are passed in changed. Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-
Ray Strode authored
Signed-off-by:
Ray Strode <rstrode@redhat.com> https://bugs.freedesktop.org/show_bug.cgi?id=105865
-