-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
found minor problem in new "any user" feature #3
Comments
Oops, thanks for raising that. Something to consider for the kalipi-menu item you suggested. Is the new user a member of the group "pi"? If not you should adjust this line in "/etc/sudoers": |
Sorry for late reply... I left the /home dir as "/home/pi/Kali-Pi/menu". |
Scratch that. It only allows "sudo reboot" and such. |
Sorry, forgot to mention to add "newuser" to a few groups: usermod -a -G sudo,ftp,kismet newuser Please let me know how your go with that |
Will do soon Re4son, thanks |
There it is. That did it |
Re4son,
I found something we missed when I tested the new user options for version 3.0 the other night.
When issuing "adduser newuser", the Kali pi repo doesn't automatically copy over. So I copied Kali-pi from "pi" to "newuser" manually. Everything seemed fine, but we forgot about something... whenever issuing "sudo" as "newuser", it says "newuser" doest exist in sudoers.
I think it's because I just did usermod to change "pi" into "newuser" while testing, instead of adding user, so everything was replaced with "newuser".
Just a heads up. Idk if it's just something I'm doing wrong or what.
-(aka) Blakk.s
The text was updated successfully, but these errors were encountered: