public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: L A Walsh <cygwin@tlinx.org>
To: "René Berber" <rene.berber@gmail.com>, mikebrady@eircom.net
Cc: cygwin@cygwin.com
Subject: Re: Question about D-Bus and cygrunsrv
Date: Tue, 26 Feb 2019 08:41:00 -0000	[thread overview]
Message-ID: <5C74E202.3010306@tlinx.org> (raw)
In-Reply-To: <q4psb6$4h1q$1@blaine.gmane.org>

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

  reply	other threads:[~2019-02-26  6:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 22:01 Mike Brady
2019-02-21 17:40 ` Mike Brady
2019-02-22 10:21   ` Corinna Vinschen
2019-02-22 15:14     ` Mike Brady
2019-02-23  0:00     ` René Berber
2019-02-26  8:41       ` L A Walsh [this message]
2019-02-27 12:37         ` Mike Brady
2019-10-22 14:07     ` Mike Brady
2019-10-22 14:33       ` Mike Brady

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=5C74E202.3010306@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin@cygwin.com \
    --cc=mikebrady@eircom.net \
    --cc=rene.berber@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).