Description of problem:
When enabling the BRLTTY damenon to start after boot, a high number of Selinux denials basically floods the system log and makes the usability of the system at least questionable. In addition, it for some reason stops Orca from speaking on the login screen. Also, BRLTTY's Bluetooth support is not working.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Run sudo systemctl enable brltty
2. Do a reboot.
3. Log in again and observe increased CPU usage and the flooded audit log, also, when Orca is enabled on the login screen, it does not speak in this case.

Actual results:
The audit log is flooded with messages like these (every of them repeats, an example of each category follows):
type=AVC msg=audit(1527847059.729:5038758): avc:  denied  { dac_override } for  pid=1174 comm="brltty" capability=1  scontext=system_u:system_r:brltty_t:s0 tcontext=system_u:system_r:brltty_t:s0 tclass=capability permissive=0
type=AVC msg=audit(1527847059.729:5038760): avc:  denied  { dac_read_search } for  pid=1174 comm="brltty" capability=2  scontext=system_u:system_r:brltty_t:s0 tcontext=system_u:system_r:brltty_t:s0 tclass=capability permissive=0
type=USER_AVC msg=audit(1527848534.716:447): pid=1131 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc:  denied  { send_msg } for msgtype=method_call interface=org.freedesktop.DBus.ObjectManager member=GetManagedObjects dest=org.bluez spid=1151 tpid=1130 scontext=system_u:system_r:brltty_t:s0 tcontext=system_u:system_r:bluetooth_t:s0 tclass=dbus permissive=0  exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
type=USER_AVC msg=audit(1527848539.734:452): pid=1131 uid=81 auid=4294967295 ses=4294967295 subj=system_u:system_r:system_dbusd_t:s0-s0:c0.c1023 msg='avc:  denied  { send_msg } for msgtype=method_return dest=:1.153 spid=1130 tpid=1151 scontext=system_u:system_r:bluetooth_t:s0 tcontext=system_u:system_r:brltty_t:s0 tclass=dbus permissive=0  exe="/usr/bin/dbus-daemon" sauid=81 hostname=? addr=? terminal=?'
type=AVC msg=audit(1527847014.839:5038653): avc:  denied  { accept } for  pid=1174 comm="server-main" laddr=127.0.0.1 lport=4101 scontext=system_u:system_r:brltty_t:s0 tcontext=system_u:system_r:brltty_t:s0 tclass=tcp_socket permissive=0

Expected results:
There are no denials and BRLTTY works.

Additional info:
Applying the following local policy fixes the issues:

module brltty_additional 1.0;

require {
	type brltty_t;
	type bluetooth_t;
	class dbus send_msg;
		class tcp_socket accept;
		class capability { dac_override dac_read_search };
}
# Bluetooth communication.
allow brltty_t bluetooth_t:dbus send_msg;
allow bluetooth_t brltty_t:dbus send_msg;
# Fixes the bugs when brltty starts after boot.
allow brltty_t self:tcp_socket accept;
# And this stops the log flood completely.
allow brltty_t self:capability { dac_override dac_read_search };

Integrating the policy additions to the BRLTTY and Bluetooth policies should not be hard, i think.