Another way would be to do per-call authentication based on digital certificates. The gatekeeper should have then access to users public keys and could verify the certificates. But it would require some work on new authenticators for the gatekeper... ----- Original Message ----- From: "Craig Southeren" <craigs@postincrement.com> Sent: Wednesday, February 04, 2004 10:41 AM > Yann, > > If there was an easy Open Source way to make NetMeeting do secure > authentication, then it would have been done years ago. > > I seem to recall that NetMeeting can do authentication if the gatekeeper > supports the T.120 protocol. There is no Open Source implementation of > this protocol, which is massively complex. > > So the short answer is that there is no way to authenticate NetMeeting > users other than IP address security, or asking the user to put their > username and password into the alias field, which can be trivially > sniffed off the wire. > > Craig > > On Wed, 04 Feb 2004 09:38:11 +0100 > Yann Klis <yklis@kaliasys.com> wrote: > > > I mean, is there a manner to tell NetMeeting to ask a password when > > authenticating to gnugk, then the gnugk take the alias and the password > > sent by NetMeeting and compare it to some values in a LDAP server? > > > > In fact, I'd like to strengthened authentication between NetMeeting EP > > and GnuGK. But, comparing IP adress and alias is not enough flexible. > > > > Thanks for your answer, ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ List: Openh323gk-users@lists.sourceforge.net Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549 Homepage: http://www.gnugk.org/
