Tag Info

New answers tagged

0

Limit their login to the TTYs using /etc/security/access.conf: -:poor_user:ALL EXCEPT tty1 tty2 # Other ttys if needed. Write a custom shell that only opens the editor (and a weak editor at that): //file: poor_shell.c #include <unistd.h> int main(void) { execl("/usr/bin/nano", "nano", "/etc/network/interfaces", NULL); } Compile, it make it ...


0

If you only want a user to be able to see, have access to, and change a single file, vi is not really an option. The reason is that anyone using vi can immediately just drop to a shell within vi and run whatever commands they want, especially if they are within vi as root, which would most certainly be the case if they were editing /etc/network/interfaces. ...


0

You don't mention if you want to keep them from viewing other files, so this may work for you. Sudo allows you to define an entry in the sudoers file that will allow a specific non-privileged user to issue a specific command with with specific arguments at elevated privilege. From the sample suoders # joe may su only to operator joe ALL = /usr/bin/su ...


2

Yes. When every user in the system has the possibility to decreace the niceness of his process, then every user can cause other processes to starve. Process priorities in the linux kernel do mean something. If you give a process the nice value of -20 it gets huge chunks of cpu time. That's why only root can decrease those values. Addition suggested by ...


1

First enable the root account by setting a password: sudo passwd Then enable manual login in LightDM (assuming 14.04): sudo tee /usr/share/lightdm/lightdm.conf.d/50-allow-manual.conf <<EOF [SeatDefaults] greeter-show-manual-login=true EOF Restart LightDM: sudo service lightdm restart Login as root. You'll have to type both username and ...



Top 50 recent answers are included