Thanks -- that worked.
On Monday, September 20, 2021 at 2:11:21 PM UTC-4 Tamás Gulácsi wrote:
> chmod 4755 is not enough. Your binary must be owned by root, to run root -
> setuid means "run as owner".
>
> Rich a következőt írta (2021. szeptember 20., hétfő, 19:54:33 UTC+2):
>
>> Yes. I tried ru
OK -=- My mistake. When you setuid a program it sets the user to the owner
of the file. So I owned the file, so it would run as me. When I did a chown
root myapplication -- it runs like it should. Thanks everyone for the help.
On Monday, September 20, 2021 at 1:54:33 PM UTC-4 Rich wrote:
> Yes
chmod 4755 is not enough. Your binary must be owned by root, to run root -
setuid means "run as owner".
Rich a következőt írta (2021. szeptember 20., hétfő, 19:54:33 UTC+2):
> Yes. I tried running an exec: cmd=exec.Command("whoami") and it came as my
> user id not root. But to set the permissi
Yes. I tried running an exec: cmd=exec.Command("whoami") and it came as my
user id not root. But to set the permissions I'd run: 'chmod 4755
myapplication'
On Monday, September 20, 2021 at 11:20:39 AM UTC-4 Tamás Gulácsi wrote:
> You mean "chown root app; chmod 4755 app" ?
>
> Rich a következő
Try:
cmd:=exec.Command("id")
If it's definitely running as root then it could be other system-level
restrictions: SELinux for example. If so, "dmesg" output may give you a
clue, logging the policy violation.
On Monday, 20 September 2021 at 16:20:39 UTC+1 Tamás Gulácsi wrote:
> You mean "chown
You mean "chown root app; chmod 4755 app" ?
Rich a következőt írta (2021. szeptember 20., hétfő, 16:57:38 UTC+2):
> I am trying to create a go program so that I can peform an action that is
> more complex than the example I have below. I can't give sudo right so run
> the application due to som
