Hello everyone,
we plan to run GnuGK in the DMZ of our universities network. The general
usecase is absolutely basic: internal users should be allowed to call
out and call other internal users, outside users should be allowed to
call internal users. This could be easily determined by an IP-based ACL.
My question is, if outside users are by default denied to call other
outside users, since I couldn't think of any scenario, in which this
would be plausible (and we of course wouldn't want to pay the traffic
for those). Do I have to secure this, too? If so, which ACL-module
should be used (SQL does provide destination-based ACLs, but AFAIK
doesn't understand netmasks, which would make the process of keeping the
tables up to date a hell)?
Best Regards,
Lars
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________________
Posting: mailto:Openh323gk-users@lists.sourceforge.net
Archive:
http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users
Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users
Homepage: http://www.gnugk.org/
