New subject: [Bug 1393649] ejabberd's unit file should not launch ejabberdctl with /usr /bin/bash

9 Nov 2016


      https://bugzilla.redhat.com/show_bug.cgi?id=1393649
Bug ID: 1393649
           Summary: ejabberd's unit file should not launch ejabberdctl
                    with /usr/bin/bash
           Product: Fedora
           Version: rawhide
         Component: ejabberd
          Severity: medium
          Assignee: lemenkov@gmail.com
          Reporter: randy@electronsweatshop.com
        QA Contact: extras-qa@fedoraproject.org
                CC: erlang@lists.fedoraproject.org, jeremy@jcline.org,
                    lemenkov@gmail.com, martin@laptop.org,
                    randy@electronsweatshop.com
        Depends On: 1393643
   External Bug ID: Github processone/ejabberd/issues/1375
Description of problem:
Currently, ejabberdctl is launched by systemd with /usr/bin/bash instead of
being launched directly. This causes the process to run in the initrc_t context
which is very permissive. Instead, systemd should launch ejabberdctl directly.
However, there are two blockers to getting this change done and working, as we
get these AVC denials with this change in place:
type=AVC msg=audit(1478751171.862:648): avc:  denied  { write } for  pid=2989
comm="async_2" name="ejabberd.pem" dev="dm-1" ino=44546
scontext=system_u:system_r:rabbitmq_t:s0
tcontext=unconfined_u:object_r:etc_t:s0 tclass=file permissive=0
type=AVC msg=audit(1478751171.863:649): avc:  denied  { write } for  pid=2989
comm="async_2" name="ejabberd.pem" dev="dm-1" ino=44546
scontext=system_u:system_r:rabbitmq_t:s0
tcontext=unconfined_u:object_r:etc_t:s0 tclass=file permissive=0
type=AVC msg=audit(1478751171.865:650): avc:  denied  { name_bind } for 
pid=2986 comm="beam" src=5349 scontext=system_u:system_r:rabbitmq_t:s0
tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket permissive=0
I've filed a bug upstream to request that they stop trying to open the certfile
in write mode[0], and I've filed a bug against selinux-policy to request that
ejabberd be allowed to use tcp port 5349[1]. Once both of those bugs are fixed,
we can proceed with dropping /usr/bin/bash presuming that we don't then hit
further AVC denials (which could happen).
Version-Release number of selected component (if applicable):
ejabberd-16.08-2.fc25.x86_64
Additional info:
[0] https://github.com/processone/ejabberd/issues/1375
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1393643
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1393643
[Bug 1393643] ejabberd is not allowed to open tcp port 5349
-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug 1393649] New: ejabberd' s unit file should not launch ejabberdctl with /usr/bin/bash