From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: preventing setup from forking
Date: Tue, 18 May 2021 11:13:23 +0200 [thread overview]
Message-ID: <22cf500b-ec2e-11fd-97f1-ad2008433851@gmail.com> (raw)
In-Reply-To: <003d01d74b61$65d99c30$318cd490$@pdinc.us>
On 17.05.2021 23:12, Jason Pyeron wrote:
>> -----Original Message-----
>> From: Jon Turney
>> Sent: Monday, May 17, 2021 4:41 PM
>>
>
> My real issue was the user was not an admin - doh!
that could be due to "setup" in the program name.
It is one of the "security" ideas of MS
Regards
Marco
next prev parent reply other threads:[~2021-05-18 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 19:59 Jason Pyeron
2021-05-17 20:40 ` Jon Turney
2021-05-17 21:12 ` Jason Pyeron
2021-05-18 9:13 ` Marco Atzeri [this message]
2021-05-18 20:39 ` Adam Dinwoodie
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=22cf500b-ec2e-11fd-97f1-ad2008433851@gmail.com \
--to=marco.atzeri@gmail.com \
--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).