Thats a jetty service (sipxconfig). I dont know how you would make that change. If you want to deny service, easier to do that at your firewall as an acl there dont you think?
even though its running on apache it might not agree with an apache acl. either way those changes would be made in an apache config (which could be deleted when an upgrade occurs) or in jetty (again, if config is replaced by a sipxecs upgrade...)... so whatever you do, document and be ready to undo it (or redo it, as the case may be). On Wed, Aug 11, 2010 at 11:50 AM, Ujjval Karihaloo <[email protected]>wrote: > On my centos, I have /etc/hosts.deny set to ALL:ALL > > > > Then, I set in hosts.allow for sshd access from certain IPs only. NO other > entry in hosts.allow. SSH seems to be properly locked down. > > > > Looks like sipX GUI config using http (port 80) and then links to https on > port 8443 seems to work from any external IP and the hosts.deny entry does > not take effect for sipX GUI access.. > > > > Any ideas? > > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
