public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: Feature request: sudo
Date: Thu, 19 Jan 2023 22:53:59 +0100	[thread overview]
Message-ID: <047d0e2f-e21a-2a8f-2bb4-e39c89762a30@towo.net> (raw)
In-Reply-To: <CAF8HOZJ9U36twWekhwtrC6w7DMdvde0z3PxrP65ExZYxDLf2Xg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]


Am 19.01.2023 um 20:17 schrieb Jochen Wiedmann via Cygwin:
> Hi,
>
> as someone who is quite used to typing
>
>    sudo do something
>
> I would really like to do the same in my CygWin bash.In my opinion,
> this could be implemented
> relatively simply, and straightforward as follows:
>
>    - Accept an array of strings with the command, that is being
> executed with administrator
>      privileges.
>    - Use the standard Windows API to execute some functionality with
> admin privileges.
>      In the current case, that functionality would be a simple exec
> with the above command line.
>
> The result would be a sudo executable without some of the configurable
> features of the
> Linux/Unix sudo (like execution without password,  or execution of
> special command lines
> without root privileges), but just the same for all practical
> purposes. I think, that a lot of users
> would benefit.
>
> Thanks,
>
> Jochen
There used to be a su tool in cygwin.
See future of su 
<https://sourceware.org/pipermail/cygwin-apps/2012-May/030226.html> and 
"su" command removed / coreutils-8.23-2 
<https://sourceware.org/pipermail/cygwin/2014-September/217105.html> for 
some discussion.

      parent reply	other threads:[~2023-01-19 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 19:17 Jochen Wiedmann
2023-01-19 20:38 ` Corinna Vinschen
2023-01-19 21:27 ` Kevin Schnitzius
2023-01-19 21:53 ` Thomas Wolff [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=047d0e2f-e21a-2a8f-2bb4-e39c89762a30@towo.net \
    --to=towo@towo.net \
    --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).