public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: crontab message "must be privileged to use -u"
Date: Wed, 18 Mar 2020 19:25:20 -0600	[thread overview]
Message-ID: <da616bfd-93d5-28ff-ccdd-6f9cb0c9803e@SystematicSw.ab.ca> (raw)
In-Reply-To: <875zf1tka7.fsf@Rainer.invalid>

On 2020-03-18 15:39, Achim Gratz wrote:
> Andrey Repin writes:
>>>> I'm in an elevated shell, but it seems crontab is doing a dumb POSIX check for
>>>> EUID=0.
>>
>>> Then wrapping it with fakesu should work (no I have not tried that).
>>
>> Cool idea, but I'm not up for recompiling crontab >.>
>> Still, thanks for the reply.
> 
> If you care to look at the package listing you might have noticed that
> there is an actual fakesu binary present that I believe does exactly
> what you were asking.

Installed libfakesu - fakesu just scans source for functions it can fake - it is
undocumented and not obvious how you are meant to run it.
One library function can implement suid/sgid exe permission bits.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

  reply	other threads:[~2020-03-19  1:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 19:54 Andrey Repin
2020-03-18 20:21 ` Achim Gratz
2020-03-18 21:06   ` Andrey Repin
2020-03-18 21:39     ` Achim Gratz
2020-03-19  1:25       ` Brian Inglis [this message]
2020-03-19  7:01         ` ASSI
2020-03-20 16:08 ` Stephen Carrier

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=da616bfd-93d5-28ff-ccdd-6f9cb0c9803e@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).