From: sjoerd@spring.luon.net (Sjoerd Simons)
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] The new D-Bus API specification
Date: Sat, 4 Mar 2006 21:15:11 +0100 [thread overview]
Message-ID: <20060304201511.GA2959@spring.luon.net> (raw)
In-Reply-To: <1141394159.4814.3.camel@aeonflux.holtmann.net>
[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]
On Fri, Mar 03, 2006 at 02:55:58PM +0100, Marcel Holtmann wrote:
> Hi Claudio,
>
> > I tested the latest bluez-utils CVS version with the recent D-Bus
> > changes and I have some comments:
> >
> > * Policy
> > I'm not sure, but I think some linux distributions use pam_console
> > instead of at_console. We sould investigate more to avoid future
> > problems. Another thing are the rules. at_console aims provide a way
> > to refer to users that are not physically sitting in front of the
> > computer. I tested send D-Bus messages from the local host or
> > connected through ssh and I didn't noticed differences. I mean, the
> > behaviour is the same. Remote users still able to send D-Bus messages.
>
> actually the at_console should be transparent between different Linux
> distributions. However we need to verify that it works on at least
> Fedora, SuSE, Debian and Ubuntu.
at_console currently doesn't work on Debian, but does on Ubuntu (using
pam-foreground not pam_console). However i intend to add pam-foreground support
to debian's dbus too, which would make at_console supported on debian too.
Sjoerd
--
The moon may be smaller than Earth, but it's further away.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-03-04 20:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 23:58 [Bluez-devel] The new D-Bus API specification Marcel Holtmann
2006-02-24 19:05 ` Marcel Holtmann
2006-03-02 21:02 ` Claudio Takahasi
2006-03-03 13:55 ` Marcel Holtmann
2006-03-04 20:15 ` Sjoerd Simons [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=20060304201511.GA2959@spring.luon.net \
--to=sjoerd@spring.luon.net \
--cc=bluez-devel@lists.sourceforge.net \
/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.