SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Well, what you can do so that all files and directories created are not group/world readable is to edit /etc/bashrc and find the line that says umask. Change that to 0077. Another thing that I could recomend for security reasons is to put each user in there own group and change the permissions on their home directores to 700. This will keep nosey people out of other people's home directories.
okay. What you can do is check your .bash_profile, .profile, or .bashrc in your home directory and find out where the system config file is. Actually, if I remeber on slackware, it may be either /etc/profile, or /etc/bash.profile. Either way, the config files in your home directory will point to it. Find it and change the umask.
well, for the users that you have already set up, you chan chmod those. If you're using the adduser script, I think that there is a config file somewhere in etc, but I would read over the man page for it because I don't know where it is off the top of my head. You could also write your own adduser script to do it if you don't want to waste the time trying to find the config file, LoL
you say i should have a bash or profile in my /home/user dir? i don't see anything like that except for a bash_history file. i take it that the /etc/bashrc or /etc/profile are global settings and the /home/user/.bashrc or /home/user/.profile would be user specific...so is it a problem i don't have any local configuration files?
the script /usr/sbin/adduser has in itself a line
defchmod=711 # home dir permissions - may be preferable to use 701, however.
i had used KUser to add the current users, after i saw this i created a test user using the adduser script and the resulting directory was 755...
anyways, still looking for another config file that adduser might refer to
noticed my shell was sh...changed it to bash and rebooted
now, the adduser script produces new home folders that are 711 but KUser still produces 755
[so my assumption that KUser was a frontend to adduser must be wrong]
didn't think there was much of a difference between the shells
You shouldn't worry if you don't have them. Most systems have them in their home directory by default but every system is different. Now, I assume that KUser is some sort of KDE application. You should be able to configure it in the kde config files which I believe are in /opt/ somewhere.
yes, KUser is an admin tool in KDE. i couldn't find anything in /opt, so i went and checked the bugs at kde...the 755 access is builtin, and the only way to change it is through ./configure at compile time (in a future release). i may be a noob, but this seems like a major flaw to me...guess i'll be using the shell
just noticed i'm not listed as a noob anymore...i'm a member. yay!!!
wonder how long ago that changed