CentOS - Feb 2017 - Centos 7 httpd Permission problems with Postfixadmin

On 02/17/2017 01:11 PM, Pete Biggs wrote:
>>   From error.log:
>>
>> [Fri Feb 17 12:56:33.478024 2017] [authz_core:error] [pid 5759] [client
>> 192.168.160.12:48290] AH01630: client denied by server configuration:
>> /usr/share/postfixadmin
> So it's an authorisation issue. In your .htaccess file change
>
>        Order allow,deny
>        Allow from all
>
> to the apache 2.4 version
>
>        Require all granted
>
> See http://httpd.apache.org/docs/2.4/upgrading.html
Thing is, I don't have an .htaccess file ANYWHERE on this system.  I 
checked.

I'll make one.

My memory may be flawed, but I think the .htaccess is a hidden file just 
change its properties.

john


On 2/17/2017 1:31 PM, Robert Moskowitz wrote:
>
>
> On 02/17/2017 01:11 PM, Pete Biggs wrote:
>>>   From error.log:
>>>
>>> [Fri Feb 17 12:56:33.478024 2017] [authz_core:error] [pid 5759]
[client
>>> 192.168.160.12:48290] AH01630: client denied by server
configuration:
>>> /usr/share/postfixadmin
>> So it's an authorisation issue. In your .htaccess file change
>>
>>        Order allow,deny
>>        Allow from all
>>
>> to the apache 2.4 version
>>
>>        Require all granted
>>
>> See http://httpd.apache.org/docs/2.4/upgrading.html
>
> Thing is, I don't have an .htaccess file ANYWHERE on this system. I 
> checked.
>
> I'll make one.
>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
>
>

On 02/17/2017 02:15 PM, John Plemons wrote:
> My memory may be flawed, but I think the .htaccess is a hidden file 
> just change its properties.
Yes, it is hidden, but 'ls -lsa' will show it.  And mlocate's
updatedb
finds them as in:

# locate .bash_history
/home/rgm/.bash_history
/root/.bash_history

which is another hidden file.

I use locate a lot.  'Where did I put the that write up on xyz?' Locate 
with grep are my friends.
>
> john
>
>
> On 2/17/2017 1:31 PM, Robert Moskowitz wrote:
>>
>>
>> On 02/17/2017 01:11 PM, Pete Biggs wrote:
>>>>   From error.log:
>>>>
>>>> [Fri Feb 17 12:56:33.478024 2017] [authz_core:error] [pid 5759]
>>>> [client
>>>> 192.168.160.12:48290] AH01630: client denied by server
configuration:
>>>> /usr/share/postfixadmin
>>> So it's an authorisation issue. In your .htaccess file change
>>>
>>>        Order allow,deny
>>>        Allow from all
>>>
>>> to the apache 2.4 version
>>>
>>>        Require all granted
>>>
>>> See http://httpd.apache.org/docs/2.4/upgrading.html
>>
>> Thing is, I don't have an .htaccess file ANYWHERE on this system. I
>> checked.
>>
>> I'll make one.
>>
>>
>> _______________________________________________
>> CentOS mailing list
>> CentOS at centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>>
>>
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>

> 
> Thing is, I don't have an .htaccess file ANYWHERE on this system.  I 
> checked.
> 
If you don't have a .htaccess file, then why have the
AllowOverride?directive in the .conf file?

Putting AllowOverride in means that every time apache retrieves a file
from that directory, *and every directory below*, it will look for a
.htaccess file in the current directory, and every directory above
(until it reaches the original directory). It doesn't cache the
information (because it can change), so it means a significant increase
in the amount of disk activity for each page. It also provides another
attack surface for naughty people.

So in general if you don't use, or intend to use, .htaccess files, then
don't put in the AllowOverride directive.

P.