You're right. The gatekeeper checks only the first alias. There are modules like RadAuth or SQLAuth (in the cvs) that can provide a better control.
I think the AliasAuth based modules could be simply extended to provide a config switch to check all aliases. But this solution will be available in 2.2.2 (or in the cvs).
----- Original Message ----- From: "Akimov Alexey" <akimov_alexey@xxxxxxx>
Sent: Tuesday, April 05, 2005 3:17 PM
I using gnugk 2.2.1 on FreeBSD 4.8.
RRQs authenticated with SQLAliasAuth
by query:
SELECT CONCAT( 'sigip:', user.ip, ':', user.port ) FROM user WHERE user.alias='%1'
Everything works fine but the following is where I get confused:
Suppose `user` table has following record:
alias ip port ----------------------------------- 1000 192.168.1.10 1720
I trying to register from 192.168.1.10 on gnugk with OpenPhone, which is configured to have correct alias "1000" and furthermore any other alias, assume 9876.
gnugk does authenticate and register not only first CORRECT alias, but also any following alias, which may in fact belong to another IP or not even present in database table.
Is this behavior correct or I just mess up with config?
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________________
List: Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
