> Dale wrote: > > OK, yes, "Stopping ignorant users." Easy enough, since the RLS > > doesn't need to enforce anything -- just ensure that not-allowed > > entries aren't written into resource-lists.xml. > > "Opportunistic" is probably a better term than "ignorant." :) > > But yes, we'll go ahead with a GUI only implementation of XX-8496. > > A hacker can always construct SIP messages to get at the data > anyway, so there is no point trying to secure against that.
That's a bit of an overstatement. If one does not have direct access to a phone to be monitored then it should be possible put proper barriers in sipXecs to truly prevent unprivileged users from monitoring others. But I agree that as a first step, locking down the GUI is the way to go. > > What we will do is allow the admin to remove the temptation > of a flashing button on the user's phone. > > > -Paul > [email protected] > > > > _______________________________________________ > sipx-dev mailing list [email protected] List > Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
