From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 59875 invoked by alias); 27 Feb 2019 10:31:34 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 59860 invoked by uid 89); 27 Feb 2019 10:31:34 -0000 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 Received: from vie01a-dmta-pe08-2.mx.upcmail.net (HELO vie01a-dmta-pe08-2.mx.upcmail.net) (84.116.36.21) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 27 Feb 2019 10:31:32 +0000 Received: from [172.31.216.235] (helo=vie01a-pemc-psmtp-pe12.mail.upcmail.net) by vie01a-dmta-pe08.mx.upcmail.net with esmtp (Exim 4.88) (envelope-from ) id 1gywUp-0007S4-Tr for cygwin@cygwin.com; Wed, 27 Feb 2019 11:31:27 +0100 Received: from helix.aillwee.com ([37.228.204.209]) by vie01a-pemc-psmtp-pe12.mail.upcmail.net with ESMTP id ywUpgC7Ky2WSsywUpgpvog; Wed, 27 Feb 2019 11:31:27 +0100 X-Env-Mailfrom: mikebrady@eircom.net X-Env-Rcptto: cygwin@cygwin.com X-SourceIP: 37.228.204.209 Received: from brady.scss.tcd.ie (brady.scss.tcd.ie [134.226.35.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by helix.aillwee.com (Postfix) with ESMTPSA id A8EA84E607; Wed, 27 Feb 2019 10:31:26 +0000 (GMT) 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 In-Reply-To: <5C74E202.3010306@tlinx.org> Date: Wed, 27 Feb 2019 12:37:00 -0000 Cc: =?utf-8?Q?Ren=C3=A9_Berber?= , cygwin@cygwin.com Content-Transfer-Encoding: quoted-printable Message-Id: <577227B8-438D-4447-8A8F-061D9AE002F0@eircom.net> References: <287EA5C9-AEDB-417D-8E1D-29405AB24325@eircom.net> <23766B16-3812-4D94-AA7C-C61C167A05C9@eircom.net> <20190222095525.GN4256@calimero.vinschen.de> <5C74E202.3010306@tlinx.org> To: L A Walsh X-SW-Source: 2019-02/txt/msg00475.txt.bz2 Thanks for the comments. I=E2=80=99ll certainly check the security side of = things. What is a bit intriguing is that another application =E2=80=94 the Avahi da= emon (see http://avahi.org) that provides ZeroConf / Bonjour service discov= ery services =E2=80=94 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), wh= ereas the Avahi daemon uses the dbus library directly. Mike > On 26 Feb 2019, at 06:51, L A Walsh wrote: >=20 > On 2/22/2019 2:16 PM, Ren=C3=A9 Berber wrote: >>=20 >>=20 >> 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 : >> - -) >>=20 >> 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. >>=20 > --- > 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. >>=20 >> 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). >>=20 > --- > Yeah, they are more than a little bit security paranoid. >=20 > 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. >=20 > 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. >=20 > 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. >=20 > There's a dbus list where they talk about development and security > issues @ >=20 > https://lists.freedesktop.org/mailman/listinfo/dbus >=20 > best of luck! >=20 >=20 >=20 >=20 -- 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