root (or sudo) access delay instead of password
from dontblink@feddit.it to linux@lemmy.ml on 21 Mar 12:13
https://feddit.it/post/15895669

Is there a way to require a user to wait a certain time instead of asking for a password every time he wants to execute a command as root or access the root / or another user account?

#linux

threaded - newest

peterg75@discuss.online on 21 Mar 12:18 next collapse

This would literally render sudo utterly useless. Sudo is meant to require password to accomplish admin tasks. In your scenario anyone using your computer can do anything without knowing the password.

Hawke@lemmy.world on 21 Mar 12:30 collapse

This is not entirely accurate; there are plenty of times when sudo does not require a password even in the default config. And there’s the nopasswd option built-in already which would already do that portion of this request.

It sounds like the OP wants to use sudo as a Molly-guard. There’s nothing wrong with that, although it may not be the right tool for the job.

mina86@lemmy.wtf on 21 Mar 15:41 next collapse

Having to type sudo already acts as a molly-guard. Whatever OP wants to do I won’t stop them, but they are doing something strange.

Enkers@sh.itjust.works on 21 Mar 18:53 collapse

While I pretty much agree, I can definitely think of a few sporadic times doing sysadmin where things have gone so significantly wrong that an enforced sanity-check on every sudo command would have been appreciated.

peterg75@discuss.online on 21 Mar 16:30 collapse

There are plenty of ways to configure Linux to circumvent sudo. I’ve even seen people who log in as root by default. I do not, however, advise anyone to do that even if it’s just, as you put it, a Molly Guard. It has prevented me personally from doing catastrophic things to my system on a number of occasions.

terminal@lemmy.ml on 21 Mar 12:31 next collapse

Do you mean the delay between when you need to re-enter the superuser password?

I found this via an LLM:

To change the delay before needing to re-enter your sudo password, follow these steps:

  1. Open the terminal and run:

    sudo visudo
    
  2. Locate the line:

    Defaults env_reset
    
  3. Add the following line below it:

    Defaults timestamp_timeout=<time-in-minutes>
    

    Replace <time-in-minutes> with the desired timeout in minutes (e.g., 30 for 30 minutes). Setting it to 0 requires a password every time, while a negative value disables the timeout entirely.

Mazesecle@lemm.ee on 21 Mar 14:20 next collapse

I’m curious, why do people make these comments? If the op wanted an answer from an LLM, they would have asked an LLM…

nawordar@lemmy.ml on 22 Mar 15:40 collapse

A modern equivalent of let me google that for you, but a more obnoxious one

turbowafflz@lemmy.world on 21 Mar 15:48 next collapse

I found this via an LLM

“Here’s a made up answer”

lka1988@lemmy.dbzer0.com on 23 Mar 15:12 collapse

And did you verify this before posting?

mark@social.cool110.xyz on 21 Mar 12:32 next collapse

@dontblink You would have to write a PAM module to do that

cypherpunks@lemmy.ml on 21 Mar 12:38 next collapse

sure. first, configure sudo to be passwordless, or perhaps just to stay unlocked for longer (it’s easy to find instructions for how to do that).

then, put this in your ~/.bashrc:

alias sudo='echo -n "are you sure? "; for i in $(seq 5); do echo -n "$((6 - $i)) "; sleep 1; done && echo && /usr/bin/sudo ’

Now “sudo” will give you a 5 second countdown (during which you can hit ctrl-c if you change your mind) before running whatever command you ask it to.

Flyswat@lemmy.ml on 21 Mar 15:47 collapse

In terms of security, an alias can be easily overridden by a user who can even choose yo use another shell which will not read .bashrc.

So this solution cannot force/require the user to comply to the delay requirement.

I was thinking maybe with a PAM module the delay can be achieved but I haven’t found one that readily does that. Maybe OP needs to implement one :)

Hawke@lemmy.world on 21 Mar 23:14 next collapse

pam_faildelay almost does it, but it only delays on auth failure. You would want something that delays on success. Might be almost as simple as “if not” on a check on pam_faildelay.

alphadont@lemmy.ca on 25 Mar 04:44 collapse

If an untrusted user is sitting at the console of a sudoer account, armed with its password, all is lost and any security has effectively been defeated already. While I do understand the concern it seems like something of a moot point.

mbirth@lemmy.ml on 21 Mar 12:39 next collapse

What purpose should this fulfil? If you are unsure whether your command is correct, double-check it before hitting the ENTER key.

Hawke@lemmy.world on 21 Mar 12:44 next collapse

I can’t find anything that quite fits your requirements.

Putting a NOPASSWD option on your sudo config should cover the removal of the password requirement, but this may be ill-advised; it is probably wiser to increase the timestamp_timeout duration.

The intentional delay is tougher, and for that it looks like you’d need to write a PAM module. pam_faildelay is very close to what you need, you’d just need to make it produce a delay on success as well as failure.

mina86@lemmy.wtf on 21 Mar 15:36 next collapse

Sure, though I advise against it. The following C program can do that:

#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>

int main(int argc, char **argv) {
	if (argc < 2) {
		fprintf(stderr, "usage: %s <command> <args>...", argv[0]);
		return EXIT_FAILURE;
	}

	printf("Executing");
	for (int i = 1; i < argc; ++i) {
		printf(" %s", argv[i]);
	}
	puts("\nPress ^C to abort.");
	sleep(5);

	if (setuid(0)) {
		perror("setuid");
		return EXIT_FAILURE;
	}

	execvp(argv[1], argv + 1);
	perror(argv[1]);
	return EXIT_FAILURE;
}

As seen in:

$ gcc -O2 -o delay-su delay-su.c
$ sudo chown root:sudo delay-su
$ sudo chmod 4750 delay-su
$ ./delay-su id
$ id -u
1000
$ ./delay-su id -u
Executing id -u
^C to abort
0

This will allow anyone in group sudo to execute any command as root. You may change the group to something else to control who exactly can run the program (you cannot change the user of the program).

If there’s some specific command you want to run, it’s better to hard-code it or configure sudo to allow execution of that command without password.

Mwa@lemm.ee on 23 Mar 15:45 collapse

Rare seeing someone using C for automation rather then Python

mina86@lemmy.wtf on 23 Mar 18:15 collapse

You cannot write setuid scripts. It must be a binary.

Mwa@lemm.ee on 23 Mar 19:44 collapse

Ohh now I get it

deadcatbounce@reddthat.com on 22 Mar 09:33 collapse

Yes; the command prefix that you’re looking for is

shutdown now ; (followed by your sudo command if you wish)

It will provide the appropriate delay before using the root command via sudo or having logged again as root (sigh)!

m33@theprancingpony.in on 23 Mar 12:22 collapse

@deadcatbounce @dontblink That's the Linux version of "press ALT+F4 to enable cheatmode" 🤣

deadcatbounce@reddthat.com on 23 Mar 16:10 collapse

Please don’t desecrate my Linux with (what I assume is) Windows talk.

Bleugh! I need a shower!

[The worst Linux users are ex Windows users; 2004 vintage here]

m33@theprancingpony.in on 23 Mar 16:34 collapse

@deadcatbounce

deadcatbounce@reddthat.com on 23 Mar 21:31 collapse

😁