All of lore.kernel.org
 help / color / mirror / Atom feed
From: guido@trentalancia.com (Guido Trentalancia)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2]: fix packagekit file context (standard location for the daemon)
Date: Wed, 27 Jun 2012 18:59:59 +0200	[thread overview]
Message-ID: <1340816399.3001.8.camel@vortex> (raw)
In-Reply-To: <1340739947.12652.7.camel@x220.mydomain.internal>

Hello again.

On Tue, 2012-06-26 at 21:45 +0200, Dominick Grift wrote:
> On Tue, 2012-06-26 at 21:39 +0200, Guido Trentalancia wrote:
> 
> > 
> > Backward-compatibility should only be considered if it can coexist with
> > compatibility with recent versions.
> 
> It can coexist.

Needless to say, if both lines coexist without a conditional expression
on the version (not supported at the moment), in the absence of any hash
verification (should fit well as an optional last field in a future
version of the file-contexts definitions), an hijacked copy of
policykitd installed in the other location would be able to run with the
same permissions as the trusted packagekitd without the user noticing
anything.

> > > Right.  I've restored the line.

Least but not last, it probably was just a bug, as since version 0.1.0
through 0.7.4, they all install by default in sbindir (which defaults
to /usr/sbin).

> > See above.

Regards,

Guido

  reply	other threads:[~2012-06-27 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20 15:56 [refpolicy] [PATCH]: fix packagekit file context (standard location for the daemon) Guido Trentalancia
2012-06-21  1:09 ` [refpolicy] [PATCH v2]: " Guido Trentalancia
2012-06-26 13:44   ` Christopher J. PeBenito
2012-06-26 13:50     ` Dominick Grift
2012-06-26 14:06       ` Christopher J. PeBenito
2012-06-26 19:39         ` Guido Trentalancia
2012-06-26 19:45           ` Dominick Grift
2012-06-27 16:59             ` Guido Trentalancia [this message]
2012-06-27 17:13               ` Dominick Grift
2012-06-27 18:28                 ` Guido Trentalancia
2012-06-27 17:32         ` Guido Trentalancia

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=1340816399.3001.8.camel@vortex \
    --to=guido@trentalancia.com \
    --cc=refpolicy@oss.tresys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.