Description of problem: When rtpproxy starts, it creates a local (UNIX domain) socket that other applications can use to control it. It also switches to its own ordinary user (rtpproxy). Unfortunately, it sets the permissions of this socket to 755, allowing only itself to write to the socket. If the controlling application runs as root, this is not a problem, but if the controlling application runs as another ordinary user, it cannot write to the socket. Version-Release number of selected component (if applicable): 1.2.1-1.el5 How reproducible: Always Steps to Reproduce: 1. Run some software that uses rtpproxy as an ordinary user, e.g. Sippy B2BUA Actual results: The software tries to connect to the rtpproxy control socket and fails with "Permission denied" Expected results: The software successfully connects to the socket. Additional info: My suggestion is to chmod the control socket to 775, which allows me to add other users to the rtpproxy group, or create a new group and add both the user running the controlling software and the rtpproxy user to this group.
Thanks for the report - this issue is confirmed. (Un)fortunately I'm using udp socket for the controlling so I wasn't aware of it.
rtpproxy-1.2.1-2.fc12 has been submitted as an update for Fedora 12. https://admin.fedoraproject.org/updates/rtpproxy-1.2.1-2.fc12
rtpproxy-1.2.1-2.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/rtpproxy-1.2.1-2.el5
rtpproxy-1.2.1-2.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/rtpproxy-1.2.1-2.fc13
rtpproxy-1.2.1-2.el4 has been submitted as an update for Fedora EPEL 4. https://admin.fedoraproject.org/updates/rtpproxy-1.2.1-2.el4
rtpproxy-1.2.1-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/rtpproxy-1.2.1-2.fc14
rtpproxy-1.2.1-2.el4 has been pushed to the Fedora EPEL 4 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update rtpproxy'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/rtpproxy-1.2.1-2.el4
rtpproxy-1.2.1-2.el5 has been pushed to the Fedora EPEL 5 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update rtpproxy'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/rtpproxy-1.2.1-2.el5
rtpproxy-1.2.1-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
rtpproxy-1.2.1-2.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
rtpproxy-1.2.1-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
rtpproxy-1.2.1-2.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
rtpproxy-1.2.1-2.el4 has been pushed to the Fedora EPEL 4 stable repository. If problems still persist, please make note of it in this bug report.