82c3939c38
A pure blacklist is not good enough, we need a whitelist mechanism as well, and the simplest way to do that is to re-use existing ACL infrastructure. This makes it simpler to blacklist say an entire block (/24) except a smaller block (eg, a /29 or even a /32). Normally you'd need to recursively split the block, so if you want to blacklist a /24 except for a /29 you'd end up with a blacklit for a /25, /26, /27 and /28. I feel that having an ACL instead of a blacklist only is clearer. Change-Id: Id57a8df51fcfd3bd85ea67c489c85c6c3ecd7b30 Signed-off-by: Jaco Kroon <jaco@uls.co.za> |
||
|---|---|---|
| .. | ||
| CHANGES-staging | ||
| UPGRADE-staging | ||
| lang | ||
| .gitignore | ||
| CODING-GUIDELINES | ||
| IAX2-security.pdf | ||
| IAX2-security.txt | ||
| Makefile | ||
| README.txt | ||
| aelparse.8 | ||
| appdocsxml.dtd | ||
| appdocsxml.xslt | ||
| astdb2bdb.8 | ||
| astdb2sqlite3.8 | ||
| asterisk-ng-doxygen.in | ||
| asterisk.8 | ||
| asterisk.sgml | ||
| smsq.8 | ||
README.txt
The vast majority of the Asterisk project documentation has been moved to the
project wiki:
https://wiki.asterisk.org/
Asterisk release tarballs contain an export of the wiki in PDF and plain text
form, which you can find in:
doc/AST.pdf
doc/AST.txt
Asterisk uses the Doxygen documentation software. Run "make progdocs" and open
the resulting documentation index at doc/api/index.html in a webbrowser or copy
the directory to a directory served by a webserver for remote access.