Andrew, You're missing the point - if you chmod /home/user to 755, *everyone* on your system can navigate to your home directory and potentially read sensitive files.
If this is not a multi-user system, the issue is not as severe; it's still a bad idea, nonetheless. A better approach is to move the content out of /home/user and just create a symlink to the content or bash alias if you want more convenience. On Mon, Jul 31, 2023 at 4:53 AM Andrew Hoff <andrew.h...@bigpond.com.invalid> wrote: > Dear Frank, > > chmod 755; I remembered immediately and did that first. I do everything > via symlinks and/or perl 5/7 scripts, e.g. a perl script lists directory > contents in index.html. As I said everything works. > > Apache is a great product and the inbuilt perl interpreter is pretty good. > I have learnt my lesson and will now use semanage to effectively document > custom settings. > > Regards, > > -- > > Andrew Hoff > 6/10 Middle Road > Maribyrnong 3032 > Victoria > Tel: 0393185581 (Please leave a message.) > Mob: 0400966178 > Email: andrew.h...@bigpond.com > > > On Sun, 2023-07-30 at 09:20 -0400, Frank Gingras wrote: > > Data in home directories is indeed a problem for shared systems, since you > have to chmod the /home/user directory. > > On Sun, Jul 30, 2023 at 8:53 AM Andrew Hoff > <andrew.h...@bigpond.com.invalid> wrote: > > Hello, > > I have resolved ALL issues. Nearly all problems were related to selinux. > It is lucky I made some notes. > > Data in home directories is not a problem. It was just selinux. > > Regards, > >
