Hello!
What happent if I do #chmod -x passwd.
Or is there better way to stop making new users.
Kids are too good to make bad things

Just do it. Then you will see. And yo will tell us what it does.

2 members found this post helpful.

It would just mean that nobody could execute the passwd program, I can't think of any consequences beyond that.

However, I would think a better thing to do would be to just "chmod 700 /usr/bin/passwd" then root could still execute it. If those bad "kids" have root, it wouldn't much matter what you did to it. Note that passwd normally has the suid bit set so normal users can use it (with sufficient privileges to write their changes).

P.S. They'd have to be root to create new users. The solution is to not give them root privileges. (useradd or adduser script front end is used to create users)

If you do not give your kids root access then they should not be able to create new users anyway.

1 members found this post helpful.

I can't still believe it is not a joke. So let me provide captcha test: on what port number service spsvd is listening on?

ok!
only problem is they boot on usb and change root passwd with chroot.
I must take wires off in computer.No more usb or dvd.
I think this is solved

I believe that in your situation, the single reasonable solution is to use encryption for your partitions.

Using a good quality flash drive as your boot drive, with the kernel and initrd, you can save here the decryption key, then unless that particular flash drive is plugged in the box, nobody can access your system and data.

Of course, that's unless your kids are NSA-grade hackers and they already hidden in your garage a super-computer having at least 10000 Threadrippers. Case when you are doomed anyway.

1 members found this post helpful.

As others have pointed out here breaking the system by removing the execute permission on the password program really makes little sense. Primarily because anyone with enough permissions to "add a user" in practical terms on Slackware that means writing to /etc/passwd, /etc/group, /etc/shadow can also simply restore the permissions on the passwd binary.

1 members found this post helpful.

This is problem with public machines in youthcenter.

I find a way (someone want know)
Install slackware with LVM in crypted disk.(no easyway to chroot)
#chmod -x passwd
#chattr +i /etc/shadow
(no seems to harm)
Thanks!

How about setting a bios admin password and restricting the bootlist to the internal disk only? That's how we did it in the old days.

Your changes to passwd and /etc/shadow are completely useless.

2 members found this post helpful.

Can't you disable USB boot? BIOS needs to be configured to be able to boot form DVD or USB.

Edit: Find those guys and try to teach them something more useful. Seems they are quite capable. Who knows? When I was kid I stolen books from bookstore. Manager caught me. Instead of calling militia he ordered me to visit bookstore an help him time to time. This is how I started to read the books.

Helou!
Like I write before.Nobody can chroot cause LVM+crypted disks.
Chroot not understand logicalvolumes .
Chattr +i they can't write shadow file.
And users not change password chmod -x passwd.
Like GazL write easyest way is old way...(bios password)
I forgotten that
I hope this enough.Some day those genious find the way..
like take battery off on motherboard.
How smart they can be
We solved this!
Many thanks !