[SOLVED] Execute script after hibernation

gregors · 12-02-2023, 07:50 PM

Hi there!

I want a user script to check how long the last "hibernation phase" is gone. E.g. the question is "how long is this system awake?"
'uptime' just gives me the time since last boot - and reading the syslog requires a user to be a member of group adm (which I don't want).

TIA

Gregor

pan64 · 12-03-2023, 05:29 AM

so you can write a script that runs as a user who is member of that group and execute it with sudo.
You can configure sudo to allow to execute only this script and nothing else.

gregors · 12-03-2023, 09:39 AM

Quote:

Originally Posted by pan64

so you can write a script that runs as a user who is member of that group and execute it with sudo.
You can configure sudo to allow to execute only this script and nothing else.

Thanks for that!

Since I always avoided using sudo I tried something else. SSH is installed on all of my boxes, so why not do a

Code:

ssh root@localhost 'bla'

All I had to do for making this possible was (as root):

Code:

cat /home/$USER/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

So ... I can go on avoiding sudo :-)

Gregor

pan64 · 12-03-2023, 09:55 AM

Quote:

Originally Posted by gregors

Thanks for that!

Since I always avoided using sudo I tried something else. SSH is installed on all of my boxes, so why not do a

Code:

ssh root@localhost 'bla'

All I had to do for making this possible was (as root):

Code:

cat /home/$USER/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys

So ... I can go on avoiding sudo :-)

Gregor

Yes, you can do that too, just it will give much more rights.

gregors · 12-03-2023, 09:59 AM

Quote:

Originally Posted by pan64

Yes, you can do that too, just it will give much more rights.

Well, yes. But for me it's just about avoiding sudo (just don't want to learn the "syntax" of sudoers), and all of this happens on a local box at home. My network is not connected to a power plant or something.

So, I don't have any security concerns. Do you?

Gregor

pan64 · 12-03-2023, 10:08 AM

Quote:

Originally Posted by gregors

Well, yes. But for me it's just about avoiding sudo (just don't want to learn the "syntax" of sudoers), and all of this happens on a local box at home. My network is not connected to a power plant or something.

So, I don't have any security concerns. Do you?

Gregor

That is funny. You don't want to add the user to the group, instead, you will give full access. Ok, I have no concerns.

MadeInGermany · 12-03-2023, 02:19 PM

sudo is easy. From
man sudoers

Quote:

dgb boulder = (operator) /bin/ls, /bin/kill, /usr/bin/lprm
The user dgb may run /bin/ls, /bin/kill, and /usr/bin/lprm-but only as operator. E.g.,
$ sudo -u operator /bin/ls

Most easy is the ALL wildcard:

Code:

echo "ALL ALL=(ALL) cat /var/log/syslog" > /etc/sudoers.d/readsyslog

Now everybody may do a

Code:

sudo cat /var/log/syslog

And you can further restrict some of the ALLs.

gregors · 12-03-2023, 02:40 PM

At a second sight at the hole I'd open and given a hint (https://wiki.debian.org/SystemGroups...ssociated_user) I decided to put $USER in the adm group.

Gregor