linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hannu Mallat <hannu.mallat@jollamobile.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] gdbus: use caller's bus name in polkit authorization check
Date: Fri, 19 Dec 2014 12:54:23 +0200	[thread overview]
Message-ID: <549403DF.4040404@jollamobile.com> (raw)
In-Reply-To: <E76B9C62-EBB2-4D6F-9918-A4D85C101332@holtmann.org>

Hi Marcel,

> so I wrote this code in 2009 as it seems. I can not even judge if my
> code is correct or your change is the correct one. It has been too
> long ago. You would need to convince me which one is the correct
> behavior when it comes to PolicyKit.

quoting polkit documentation for subject struct,

     "This struct describes subjects such as UNIX processes. It is
     typically used to check if a given process is authorized for
     an action."

so as far as I can see, the struct should describe the caller of
the D-Bus method, not bluetoothd itself, if the idea is to limit certain
methods to authorized callers only.

In the end I don't know if polkit offers much over D-Bus daemon based
authorization, and I chose not to use polkit for my needs, but wanted to
point out the issue nevertheless if someone else might face the same
problem.

BR,
H.

      reply	other threads:[~2014-12-19 10:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 11:51 [PATCH] gdbus: use caller's bus name in polkit authorization check Hannu Mallat
2014-12-19  7:57 ` Hannu Mallat
2014-12-19 10:15 ` Marcel Holtmann
2014-12-19 10:54   ` Hannu Mallat [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=549403DF.4040404@jollamobile.com \
    --to=hannu.mallat@jollamobile.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).