On 03/06/2015 02:59 PM, Hilario Fochi wrote:
> On Monday, March 2, 2015 at 9:56:10 AM UTC-3, Frank Bergkemper wrote:
>> Am 25.02.2015 um 20:17 schrieb Hilario Fochi:
>>> On Thursday, February 5, 2015 at 1:52:17 AM UTC-2, Ashley wrote:
>>>> Hi Guys,
>>>>
>>>> I successfully got bareos-webui working in Centos 7.
>>>>
>>>> Make sure you have epel installed:
>>>>
>>>> yum install epel-release
>>>>
>>>> I used the contrib repo from RHEL 7 as there was no Centos 7 contrib Repo 
>>>> yet.
>>>>
>>>> Also you need to edit /etc/httpd/conf.d/bareos-webui.conf and update the 
>>>> Allow From syntax to the new apache 2.4 syntax like below
>>>>
>>>> #   Deny from all
>>>> #   Allow from localhost
>>>> #   Allow from ::1
>>>> Require all granted
>>>
>>> Hello Ashley.
>>> I confirm that bareos-webui did install in Centos 7 with epel-release.
>>>
>>> Initially it presented a "Forbidden You don't have permission to access 
>>> /bareos-webui/statistics/ on this server"
>>> It only worked after I inserted the "Require all granted" line as you 
>>> instructed.
>>>
>>> It also presented connection failure to postgresql due to a SELinux 
>>> restriction.
>>> The solution as suggested by SELinux alert is to set a SELinux boolean:
>>> sudo setsebool -P httpd_can_network_connect 1
>>> sudo setsebool -P httpd_can_network_connect_db 1
>>>
>>> Frank Bergkemper:
>>> May I kindly suggest that you update your installation information on 
>>> github.com (INSTALL.md file) to include these instructions? 
>>> While there you could also include the information that on RedHat, the 
>>> bareos-webui apache configuration file should be in /etc/httpd/conf.d 
>>> instead of /etc/apache2/conf.d
>>>
>>
>> Hi Hilario,
>>
>> SELinux stuff excluded, mostly done with the new release, I guess.
>>
>> Steps to do, if SELinux is enabled, will be added to the documentation
>> after some testing with latest changes.
>>
>> If you already have done that or would like to, you are welcome to
>> contribute something.
>>
>> Frank
>>
>> -- 
>> Frank Bergkemper                           frank.bergkemperATdass-it.de
>> dass IT GmbH                               Phone:  +49.221.3565666-94
>> http://www.dass-IT.de/                     Fax  : +49.221.3565666-10
>>
>> Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRB52500
>> GF: Stephan Dühr, Maik Außendorf, Jörg Steffens, Philipp Storz
> 
> Frank,
> I will continue to test the bareos-webui and will report any SELinux issues 
> or solution I may have.
> I will indeed install it with SELinux enforcing because it is the correct and 
> sensible way to do it. As soon as we figure-out all the settings, than the 
> rpm install scriptlet should be updated to fix it. Also the install docs must 
> have a section dedicated to SELinux and how to manually set it.

Simply adding setsebool to %post may not be compliant with common Fedora/EPEL 
packaging
Guidelines and may also cause other problems if not done properly. While Bareos 
Packages
do not necesarily need to comply to them, nevertheless it's better to check how 
to do
that properly. Some popular EPEL packages like drupal or wordpress don't have 
any setsebool
in %post. Others have an additional -selinux package, for example 
dokuwiki-selinux, but
that does only set contexts.

See http://fedoraproject.org/wiki/SELinux_Policy_Modules_Packaging_Draft
and some interesting remarks here: 
https://bugzilla.redhat.com/show_bug.cgi?id=801752

Regards

-- 
  Stephan Dühr                              stephan.du...@bareos.com
  Bareos GmbH & Co. KG                      Phone: +49 221-630693-90
  http://www.bareos.com

  Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
  Komplementär: Bareos Verwaltungs-GmbH
  Geschäftsführer: S. Dühr, M. Außendorf,
  J. Steffens, Philipp Storz, M. v. Wieringen

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to bareos-users+unsubscr...@googlegroups.com.
To post to this group, send email to bareos-users@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to