Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Im looking to change GID numbers for certian groups.
My initial thought is to open /etc/group and change the number to what it needs to be. My concern might be for files that were created under the old group ID. Similar to changing a UID. Any thoughts on this?
The reason I am doing this, is because I am trying to make several servers that have the same UID's and GID's (same group names and user names).
But something tells me just editing /etc/group will do fine. The UID's however would be a little more involved (finding all files and modifiying them).
I wouldn't recommend starting at the root directory. You will waste a lot of time doing it that way. Searching for group owned files in /proc, /sys, /mnt or /dev isn't what you want to do. Excluding certain directories can make the command too complicated.
You could use a form like:
find /home /tmp /var /usr ...
instead to apply it on directories that you know have the group's files.
Also, use su or sudo instead, and log in as a normal user. It is a good habit to get into. (And enforced if you have Ubuntu)
That's an excellent point, and some great advice. I will give it a shot on a few bogus users as well as groups and files. I forget sometimes that being logged in as root is not always the "wise" thing to do.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.