[Wolves] Couple of probs with directory access and putty colours
drinky76 at yahoo.com
Mon Apr 27 15:23:02 UTC 2009
----- Original Message ----
> From: Wayne <waynelists at machx.co.uk>
> To: Wolverhampton Linux User Group <wolves at mailman.lug.org.uk>
> Sent: Monday, 27 April, 2009 15:51:43
> Subject: [Wolves] Couple of probs with directory access and putty colours
> Work progresses with my Fedora 10 /Exim/Mysql/Apache server but a couple
> of wierd things.
> Trying to get Eximon to work, it could't access /var/log/exim and indeed
> the permissions seemed wrong so
> I changed them to 777 and chown exim, and now they work.
> But as user I cannot see the contents (via winscp), but can as root.
Not used eximon to be honest. Root can always see everything. The usual way of getting around such permission problems is to add the user to a group (either the group that owns the files, or a new one) and making sure that group can do what they need to, rather than blanket allowing everyone to do anything.
As explained when you had a break in, you would be much better off using CentOS rather than Fedora for a live server. CentOS *is* RHEL with the branding changed, they even compile with the same options RH use. Fedora end of life their releases a month before their second subsequent release. Based on 6 monthly releases, that means you stop getting security updates 11 months after release. Not a good idea to expose that to the Internet unless you plan to rebuild every year.
Also, you just made your Exim log directory world writable. Bad idea to do that to any directory.
> Putty thing - trying to get Webalizer working, i've created the
> directory as /var/www/html/usage and change the permissions
> and ownership to apache, but cannot access it via browser (403). In
> putty I see the directory is highlighted in green, but cannot find
> any explantion of what the colors mean in putty (how to change them -
> but not what they are!).
Ignoring the PuTTY stuff, this may well be down to an Apache configuration directive. If you look in /etc/httpd/conf.d/ there is probably a webalizer file which permits access only to 127.0.0.1. In any case, reading /var/log/httpd/error.log will tell you what the problem is, though perhaps not in explicit enough detail to work out which directive is the problem without some trial and error.
More information about the Wolves