Bug 1002754 - ejabberd: selinux prevents binding to admin ports 5280 and 5281
Summary: ejabberd: selinux prevents binding to admin ports 5280 and 5281
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: ejabberd
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-29 22:08 UTC by Jim Radford
Modified: 2015-06-29 12:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 12:18:56 UTC
Type: Bug


Attachments (Terms of Use)

Description Jim Radford 2013-08-29 22:08:49 UTC
Description of problem:

The server won't start.

type=AVC msg=audit(1377717372.581:42): avc:  denied  { name_bind } for  pid=877 comm="beam.smp" src=5280 scontext=system_u:system_r:rabbitmq_beam_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket

type=AVC msg=audit(1377805767.023:2846): avc:  denied  { name_bind } for  pid=8338 comm="beam.smp" src=5281 scontext=system_u:system_r:rabbitmq_beam_t:s0 tcontext=system_u:object_r:unreserved_port_t:s0 tclass=tcp_socket

To reproduce comment in the admin interface.

  {5280, ejabberd_http, [http_bind, {ip, {127,0,0,1}}]},

and similarly for SSL and 5281.

Additional info:

I was able to work around these buy running:

  semanage port -a -t jabber_client_port_t -p tcp 5280
  semanage port -a -t jabber_client_port_t -p tcp 5281

Maybe these should have their own class jabber_admin_port_t?  Either way, these are standard ports and ejabberd should be allowed to listen on them.

Comment 1 Juan Orti 2014-02-24 12:59:04 UTC
It happens in F20

ejabberd-2.1.13-7.fc20.x86_64
selinux-policy-targeted-3.12.1-122.fc20.noarch
selinux-policy-3.12.1-122.fc20.noarch

Comment 2 Fedora End Of Life 2015-05-29 09:21:11 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-29 12:18:56 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.