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:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=RFkhkcyOcfVtRmqE7d9rzXcnVMttpM
	bUO48rcj6N1QP2ysT0/gwfp+eXy4JgwasL44MLlH2Hpcrto8eKSYYYZwtHaYPEXV
	xamWFYJIyfwRpnx28nkzvcEHWJVlq9fuEo8G/52tabZT+jG+dQhqCbtmznLmcCDs
	L5WTv5Xw97jUE=
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:to:from:subject:date:message-id:references
	:mime-version:content-type:content-transfer-encoding
	:in-reply-to; s=default; bh=lSC7vnNzlWUwZGTTqf8LAcnKfAQ=; b=ZjlL
	stH7OHCS5qkQ5WT3sKZaIlEIPjfJatSzwczpbBQVagTtkESk6PrQilgtx1Gt5xx6
	kGRr6JhuBaM3HBkDf7IdInEq6HhMLTVCGfZBHYG1MuDoQ3X+xJWiTlzBhG6Sx9Fr
	cmIfeZAWe4EqmuYjR0mbcZ9O5Z3Rfbb8M9iX2ys=
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=-3.6 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA,FREEMAIL_FROM,GIT_PATCH_2,KAM_LAZY_DOMAIN_SECURITY autolearn=ham version=3.3.2 spammy=H*u:5.1, H*UA:en-US, H*u:en-US, H*r:Unknown
X-HELO: blaine.gmane.org
To: cygwin AT cygwin DOT com
From: =?UTF-8?Q?Ren=c3=a9_Berber?= <rene DOT berber AT gmail DOT com>
Subject: Re: Question about D-Bus and cygrunsrv
Date: Fri, 22 Feb 2019 16:16:05 -0600
Message-ID: <q4psb6$4h1q$1@blaine.gmane.org>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.0
Openpgp: preference=signencrypt
In-Reply-To: <20190222095525.GN4256@calimero.vinschen.de>
X-IsSubscribed: yes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 2/22/2019 3:55 AM, Corinna Vinschen wrote:

>>> On 20 Feb 2019, at 21:50, Mike Brady <mikebrady AT eircom DOT net> 
>>> wrote:
>>> 
>>> Hi there. I'm trying to set up Shairport Sync as a CYGWIN 
>>> service, and I'm trying to use cygrunsrv.
>>> 
>>> Briefly, I can get everything to work properly except the
>>> D-Bus interface -- when shairport-sync is installed as a
>>> service, it can't "own" a well-known name on the "system"
>>> D-Bus.
>>> 
>>> I built a configuration and installer for shairport sync 
>>> essentially by copying the avahi-daemon-config file.
>>> 
>>> The Avahi deamon uses the system D-Bus successfully under the 
>>> username "SYSTEM" and without (AFAICS) changing IDs. But for 
>>> the life of me, I can't get Shairport Sync to work the same 
>>> way.
>>> 
>>> Incidentally, if I change the D Bus policy file for Shairport 
>>> Sync to be allowed to own its well-known name on D Bus when 
>>> running under the logged in account, everything is peachy.
[snip]
> You have been heard, but I have not the faintest clue what d-bus 
> or, FWIW, avahi are doing.  Ideally, if you could break down the 
> problem to a simple, self-contained testcase which shows what 
> exactly is not working on a plain libc level, help may be possible 
> :}

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.

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).
- -- 
R.Berber
-----BEGIN PGP SIGNATURE-----

iHUEAREIAB0WIQSYcjiGOQ+69Vq++Cv/3GNYQL5I5AUCXHB0nQAKCRD/3GNYQL5I
5KDQAP9dD7Rd+qF7Z4OtcaRpljiYnji25Bxr5oQmXOkkf1oSDAD+P+sqFq3MQbTC
H4+rHD6Bepj4DPx3VD3T6DQHGy5POOQ=
=YDL0
-----END PGP SIGNATURE-----


--
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