public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Cygwin installation issues with Powerbroker
Date: Sat, 08 Apr 2017 07:27:00 -0000	[thread overview]
Message-ID: <87bms7bbqp.fsf@Rainer.invalid> (raw)
In-Reply-To: <CACER5asX+JixLUVi+fUwU2_yt8nqeaj-23nS4uU=LgLRF_vzPw@mail.gmail.com>	(Akshay Belle's message of "Tue, 4 Apr 2017 12:39:23 -0400")

Akshay Belle writes:
> I am trying to use cygwin on my office laptop, which as a software
> called powerbroker that provide admin privileges for installation of
> third party software like cygwin. Powerbroker has worked well with all
> other software installations, however cygwin is not installing
> correctly with powerbroker.

It seems to me that PowerBroker, advertising itself as providing
application based policies, would need specific rules for Cygwin.  This
would either need cooperation from your IT department or even
enhancements from BeyondTrust.

> 2017/04/04 11:52:56 running: C:\cygwin\bin\dash.exe
> "/etc/postinstall/0p_000_autorebase.dash"
>       0 [main] dash 10092 fork: child 20984 - died waiting for dll
> loading, errno 11

It seems that PowerBroker works by inserting itself into every process
image.  That's not going to work.

Until Beyond Trust comes up with a fix, I'd say PowerBroker should be
added to the BLODA.

https://cygwin.com/faq/faq.html#faq.using.bloda


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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:[~2017-04-08  7:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 16:39 Akshay Belle
2017-04-08  7:27 ` Achim Gratz [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=87bms7bbqp.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.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).