[asterisk-dev] Introduction to ASA - the Asterisk Security Architecture

Tzafrir Cohen tzafrir.cohen at xorcom.com
Tue Oct 14 09:41:18 CDT 2008

On Tue, Oct 14, 2008 at 11:07:02AM +0100, Grey Man wrote:
> On Mon, Oct 13, 2008 at 3:45 PM, Johansson Olle E <oej at edvina.net> wrote:
> >
> > I don't think you've read the document. This goes way beyond what
> > you can control in the dialplan. One of the things you can't control
> > there is SIP transfers and subscripts, just as an example. Or manager
> > actions.
> >
> > /O
> >
> I read it.
> I didn't find the requirements compelling enough to embark on massive
> re-architecture operation. You are very correct that there are some
> things that currently can't be controlled with Asterisk and SIP
> transfers is the classic one, a great addition to Asterisk would be
> able to control which contexts are permitted to accept SIP transfers.

I don't think that dialplan contexts are enough to control
authorization. They might work well if we assume that nobody can change
the dialplan. But this assumption is incorrect:

1. Originating a call to an application is, in fact, a generation of a
temporary context.

2. The manager interface today has an option to update/create a context.

3. System should allow you to manually edit extensions.conf . That is:
if you were given temporary control of part of the dialplan, you could
elavate this further.

Imagine that the company of Alice and Bob hosts its PBX at your
Asterisk server. And on the same Asterisk Eve is also hosted. How can we
still let Alice and Bob talk and prevent Eve from doing nasty stuff?

               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir

More information about the asterisk-dev mailing list