I have a question. Many H323 clients/endpoints (such as Netmeeting) do not support the H323CryptoToken method of authentication (in the H235 RAS call setup). You just put in an alias name, and that will be bound to your IP address when you register with the H323 gatekeeper.
My problem is: how do I prevent a malicious endpoint from grabbing someone else's alias name? with Netmeeting for example you can just set the alias to whatever you like.. Of course you can define an alias:IP address mapping in the gatekeeper, so you can hard-code an alias to an IP address. But this does not address say people with dialups, PPPoE connections, or DHCP leased IP's. So my question is: is there no solution to authenticating endpoints properly? or am I just stupid? --- Orlando Andico <[EMAIL PROTECTED]> Mosaic Communications, Inc. _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] Fully Searchable Archives With Friendly Web Interface at http://marc.free.net.ph To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
