I think most endpoints that support MD5 will also support CAT,
otherwise there will be interop problems with Cisco AAA framework.
But if you really want to provide MD5 authentication through radius
you need to define your own radius attributes to send fields required
to build MD5 hash (generalID,timestamp) and to verify the hash built
by radius server (md5 hash).
You can do it by deriving your own class from RadAuth
and either overriding Check methods (gk 2.0) or AppendUsernameAndPassword (gk 2.2)
to scan for additional cryptoTokens and append custom attributes.
PS: I think another way - building direct SQL authenticator or something similar - would
be a better choice in this case.
----- Original Message -----
From: "Aivis Olsteins" <aivis@datatechlabs.com>
Sent: Saturday, November 15, 2003 1:59 PM
> Back to old issue:
>
> I believe there still will be lots of endpoints supporting H.235 in form of
> MD5. Apart from modifications needed in radius server, we also need to
> modify something in gk, right? Otherwise it just complains about missing
> m_tokens and rejects a call... What should be modified there? Any ideas?
-------------------------------------------------------
This SF. Net email is sponsored by: GoToMyPC
GoToMyPC is the fast, easy and secure way to access your computer from
any Web browser or wireless device. Click here to Try it Free!
https://www.gotomypc.com/tr/OSDN/AW/Q4_2003/t/g22lp?Target=mm/g22lp.tmpl
_______________________________________________
List: Openh323gk-users@lists.sourceforge.net
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
