Created attachment 364014 [details] Patch for asterisk spec file to change file ownership Description of problem: In order to run the 2.0 branch of the Asterisk GUI, /etc/asterisk and /usr/share/asterisk need to be writeable to the asterisk user. Is the best way to accomplish this requirement just make these directories and their contents be chown asterisk:asterisk? Also, /etc/asterisk/manager.conf should probably be mode 600 as it can contain usernames and passwords to the Asterisk Management Interface. There may be other files that should probably be chmod 600 but I only know about manager.conf because I've been working on packaging asterisk-gui Attaching a patch to the spec file that changes the ownership of the proper files. I've built 1.6.1.6-1 in a private Koji instance and this patched spec works with my asterisk-gui RPM. Thanks for packaging Asterisk. Version-Release number of selected component (if applicable): asterisk-1.6.1.6-1.fc11.x86_64
Andrew what do you think about restricting the permissions to 0640 for files and 0750 for directories? Is there a reason that something that's not running as root or asterisk would need to access the files?
Sounds good to me. I can't think of a reason why another user would need access.
I've updated the package with the permission/ownership changes, could you download the RPMs from koji and see how they work for you? I've also updated to 1.6.1.7-rc2 and some other changes. http://koji.fedoraproject.org/koji/taskinfo?taskID=1735445
Works like a charm with my asterisk-gui RPM. Everything seems to be working as expected.
asterisk-1.6.1.7-0.1.rc2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/asterisk-1.6.1.7-0.1.rc2.fc11
asterisk-1.6.1.7-0.1.rc2.fc11 has been pushed to the Fedora 11 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 asterisk'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10395
asterisk-1.6.1.7-0.4.rc2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/asterisk-1.6.1.7-0.4.rc2.fc11
asterisk-1.6.1.7-0.4.rc2.fc11 has been pushed to the Fedora 11 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 asterisk'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10724
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 WONTFIX if it remains open with a Fedora 'version' of '11'. 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 prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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. Thank you for reporting this bug and we are sorry it could not be fixed.