<html>
<head>
</head>
<body>
Actually as root I change "/home/jl" to be 770 or 750 and then after an undetermined
but compartively short period of time it gets chanked back to 755 which means
any other user can look into my "home."<br>
<br>
Following is an example of the command I used cut an pasted from a genuine
CLI.<br>
<br>
[jl@localhost jl]$ su<br>
Password: <br>
[root@localhost jl]# chmod 750 /home/jl<br>
<br>
David Jackson wrote:<br>
<blockquote type="cite" cite="mid:1319.63.165.194.52.1022103936.cqhost@webmail.cqhost.com">
<pre wrap="">Ed --<br>You missed Joe's problem, he see the perm to say 755 and the Mandrake<br>changes them back to say 750? Which as someone else suggested (beside myself)<br>a cron job is running to change perms as a secruity practice.<br><br>David<br><br></pre>
<blockquote type="cite">
<pre wrap="">On Wed, 2002-05-22 at 14:08, Joe Linux wrote:<br></pre>
<blockquote type="cite">
<pre wrap="">After a great deal of time consuming effort, I thought I had the <br>Mandrake permissions problem solved, but now they have come back as <br>before -<br>755. It seems rather odd to me that on a multi-user system that one <br>user can peer into another users files, and you can't do anything to <br>stop it.<br>Mandrake Linux is like a glass house with no window shades.<br></pre>
</blockquote>
<pre wrap=""><br>No, its most certainly not a "glass house" as you describe.<br><br>What exactly are you trying to do?<br><br>If you want to make a particular directory (or even an entire home<br>directory and all its contents) private, then its very easy. Just use:<br><br> chmod 700 /home/user_name/dir_to_make_private<br><br>or<br><br> chmod 700 /home/user_name<br><br>and you're done.<br><br>If this gives you problems, then things to check are:<br><br> (1) What kind of filesystem are you using? If you're using some <br> kind of MS FAT filesystem then this may not work since (AFAIK) <br> some FAT filesystems do not fully support Unix-style (POSIX) <br> permissions. And if thats the case, then shame on *you* for <br> choosing to use a non-Unix filesystem and then demanding that it<br> support POSIX permissions.<br><br> (2) Mount point: If the directory that you are trying to alter <br> the permissions on is itself a mount point for a file sys
tem, <br> then read "man chmod" and "man mount" for the details <br> (permissions are set at mount time).<br><br>If you have more questions about chmod for the group, then I suggest<br>you provide a more exact description of what you're trying to<br>accomplish and *exactly* what commands you're using.<br><br>hth,<br>Ed<br><br><br>-- <br>Edward H. Hill III, PhD | Email: <a class="moz-txt-link-abbreviated" href="mailto:ed@eh3.com">ed@eh3.com</a>, <a class="moz-txt-link-abbreviated" href="mailto:ehill@mines.edu">ehill@mines.edu</a><br>Post-Doctoral Researcher | URLs: <a class="moz-txt-link-freetext" href="http://www.eh3.com">http://www.eh3.com</a><br>Division of ESE | <br><a class="moz-txt-link-freetext" href="http://wasser.mines.edu/people/edhill.php">http://wasser.mines.edu/people/edhill.php</a> Colorado School of Mines | <br>Phone: 303-273-3483<br>Golden, CO 80401 | Fax: 303-273-3311<br>Key fingerprint = 5BDE
4DA1 66BE 4F7B BC17 3A0C 932B 7266 1E76 F123<br>_______________________________________________<br>CLUE-Tech mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:CLUE-Tech@clue.denver.co.us">CLUE-Tech@clue.denver.co.us</a><br><a class="moz-txt-link-freetext" href="http://clue.denver.co.us/mailman/listinfo/clue-tech">http://clue.denver.co.us/mailman/listinfo/clue-tech</a><br></pre>
</blockquote>
<pre wrap=""><!----><br><br></pre>
</blockquote>
<br>
</body>
</html>