X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id
	:references:to; q=dns; s=default; b=xU6K1vLbWUg+jlBRaRg3ZiLxErsf
	0r1L+CzpJHTLsep5iVPlfquPwf3HBLNvMMRaw7hlV4iiDR3E9IpjGuiOr+O8ZrpK
	eXAs/c+cAs8i3wkYbZt5eBVRozFJtKj0MmXeigJBph+6rJlMZmdKtE0x83/NYLIS
	NWkHDz1iBYxRVac=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:content-type:mime-version:subject:from
	:in-reply-to:date:cc:content-transfer-encoding:message-id
	:references:to; s=default; bh=EGko1anfSkmhIC23SqHMKkHXc20=; b=Zp
	XqNFM0UWzQ3L0kEFaI8a8bucnRJocty26OVK8l7WUjDH1xDeRbk2HY9xmIhBzYT1
	z9dTloQsbwzYlA5vISL+a8pq90uZVbHnmO2uSxVNaC7KmcZPw6myyCB5ntFmajHN
	QUBIrfQV0NPT3nxY1qAX/nnH21+3eBGtBXQLzml7w=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-6.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 spammy=Hx-languages-length:2995, mike, gio, intriguing
X-HELO: vie01a-dmta-pe08-2.mx.upcmail.net
X-Env-Mailfrom: mikebrady AT eircom DOT net
X-Env-Rcptto: cygwin AT cygwin DOT com
X-SourceIP: 37.228.204.209
Content-Type: text/plain;	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Subject: Re: Question about D-Bus and cygrunsrv
From: Mike Brady <mikebrady AT eircom DOT net>
In-Reply-To: <5C74E202.3010306@tlinx.org>
Date: Wed, 27 Feb 2019 10:31:24 +0000
Cc: =?utf-8?Q?Ren=C3=A9_Berber?= <rene DOT berber AT gmail DOT com>, cygwin AT cygwin DOT com
Message-Id: <577227B8-438D-4447-8A8F-061D9AE002F0@eircom.net>
References: <287EA5C9-AEDB-417D-8E1D-29405AB24325 AT eircom DOT net> <23766B16-3812-4D94-AA7C-C61C167A05C9 AT eircom DOT net> <20190222095525 DOT GN4256 AT calimero DOT vinschen DOT de> <q4psb6$4h1q$1 AT blaine DOT gmane DOT org> <5C74E202 DOT 3010306 AT tlinx DOT org>
To: L A Walsh <cygwin AT tlinx DOT org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id x1RAViZ6024087

Thanks for the comments. I’ll certainly check the security side of things.

What is a bit intriguing is that another application — the Avahi daemon (see http://avahi.org) that provides ZeroConf / Bonjour service discovery services — also uses the D-Bus system bus and it works fine as a cygrunsrv-based daemon. The difference between the two applications with respect to D-Bus is that Shairport Sync uses the high-level GDbus interface that is part of GIO (https://developer.gnome.org/gio/stable/ch01.html), whereas the Avahi daemon uses the dbus library directly.

Mike

> On 26 Feb 2019, at 06:51, L A Walsh <cygwin AT tlinx DOT org> wrote:
> 
> On 2/22/2019 2:16 PM, René Berber wrote:
>> 
>> 
>> My guess is that its a permission problem: D-Bus by default on Windows
>> uses unix sockets (fills up your temp directory with those pesky files :
>> - -)
>> 
>> In Cygwin the temp directory has the sticky permission (t), but the
>> socket file created by the server most likely doesn't have access for
>> anybody else.
>> 
> ---
>    I'm not sure, but I'd think dbus demon would be enabled to
> talk to the system socket
>> Check those permissions to maybe get a clue.
>> 
>> The problem comes from upstream, I'm just not sure because I used to
>> build my own, patched, version of DBUS (for a workaround which is to
>> use tcp, not unix sockets... but the Windows maintainer says "nobody
>> uses tcp sockets on Windows", and then they "improved" security which
>> is why I suspect access permissions).
>> 
> ---
>    Yeah, they are more than a little bit security paranoid.
> 
> I'd like to get the dbus sessions between my desktop & server to talk --
> like when I am running an X-app, and press help, it really would be
> better if it brought up the browser on my desktop instead of one
> on the server via X.
> 
> I had hopes as one of their examples specifies tcp in the protocol
> field, but supposedly the tcp doesn't work and likely won't due to
> security concerns -- mainly because the bus architecture was structured
> around the idea of an internal HW bus -- where normally there isn't
> much in the way of security.  If they allowed it to be open to
> a network, then they think everyone on the internet will have access
> and that dbus will be blaimed for a security problem.
> 
> I did mention that some people use closed nets between machines
> and should be allowed to use dbus to talk between them where desirable,
> but he thinks that most hand-held users wouldn't know how to isolate
> a net.  On top of that, dbus doesn't have the ability to categorize
> if the net is public, private(home) or enterprise(work).  Seemed
> like a pain to get working for what would be a plus for me, but
> not sure about demand, not to mention working with such paranoid
> folk really can be frustrating.
> 
> There's a dbus list where they talk about development and security
> issues @
> 
> https://lists.freedesktop.org/mailman/listinfo/dbus
> 
> best of luck!
> 
> 
> 
> 


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple