24 Replies Latest reply on Jan 25, 2007 2:04 AM by normanr

    NTLM

      Hi all! Download and install version 3.0 from 29/06/2006, integrated with the domain. On client Pandion has applied a patch, but it all the same does not wish to be connected I use NTLM.

      In a server broad gully warn.log such line is written:

      2006.07.02 14:04:26 Client wants to do a MECH we don''t support: ''NTLM''[/i]

      Client log is written:

      EVNT: Connecting to jabber

      SENT:

      EVNT: Disconnected[/i]

       

      I Ask the help for the decision of the given problem.

        • Re: NTLM
          slushpupie

          Did you modify the source for Wildfire? It does not support NTLM out of the box.  In fact, the server is only stating it accepts the PLAIN method.  Pandion did the incorrect thing (maybe on purpose?) and send an auth using the NTLM method anyway. 

           

          Wildfire as of version 3.0.0 has support for GSSAPI (Kerberos), which in an Active Directory setup is possible to use.  But it is very very experimental.  No documentation has been written on how to use it (yet! Im working on it!), but if you can read the source you should be able to figure a good chunk of it out.  However, GSSAPI and Kerberos are not NTLM. If you are using the older NT style domain, you will need to modify Wildfire to support it.  A few people have done this, so it is possible.

          • Re: NTLM

            I am sorry - I do not own English in full. Could not understand your message completely.

            What patch needs to be applied to Wildfire? You could not give me more precise instructions?

            Thanks that have responded to my problem.

              • Re: NTLM
                slushpupie

                What is your native language? Maybe someone here speaks it and can help translate. 

                 

                Wildfire does not have support for NTLM right now.  I know at least one user has added support for it, but other than that I wont be much help for NTLM.  Read JM-281 for some more details.

                  • Re: NTLM

                    My native language - Russian.

                    JM-281 I already for a long time read... Initially I have established version 2.6.2, have applied patches and all worked for me in a test mode... Then I have been very borrowed and have not introduced system in public using. About one month I did not concern a server on which worked wildfire, and then have found out that the server does not function... After start service automatically stopped in 3-5 minutes.

                    Has now seen that in version 3.0.0 have corrected a problem with NTLM and I have decided to reinstall all anew... But now I can not achieve former work automatic login.

                  • Re: NTLM

                    I earlier read this topic... On version 2.6.2 at me all has turned out... But then the jabber-server has given failure. Now on version 3.0.0 I can not achieve functionality in any way.

                  • Re: NTLM

                    I have updated my libs at http://norman.rasmussen.co.za/dl/sasl-sspi/ to support NTLM in Wildfire 3.0+ for Windows.  That should get everyone that was using NTLM in 2.6.2 back on their feet with the new version.

                    • Re: NTLM

                      ??, ????????? ???????! ...??? ?????? ? ????? ???????!

                       

                      Sorry:

                      ??, many thanks!... Now download also I shall start to test!

                      • Re: NTLM

                        Nothing has turned out

                        At attempt to incorporate a server takes off for a miss

                        Here a broad gully of the console of a server:

                        *

                        Wildfire 3.0.1

                        Admin console listening at:

                          http://jabber:9090

                          https://jabber:9091

                        #

                        1. An unexpected error has been detected by HotSpot Virtual Machine:

                        #

                        1. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d9cf640, pid=2052, tid=1552

                        #

                        1. Java VM: Java HotSpot(TM) Server VM (1.5.0_07-b03 mixed mode)

                        2. Problematic frame:

                        #

                        1. An error report file with more information is saved as hs_err_pid2052.log

                        #

                        1. If you would like to submit a bug report, please visit:

                        2.   http://java.sun.com/webapps/bugreport/crash.jsp

                        #

                        *

                          • Re: NTLM

                            This should be fixed in v5.  Post the error logs if you have any furthur problems.

                             

                            BTW: With Wildfire 3.0, there is no need to patch Pandion.

                            • Re: NTLM

                              FYI: I''ve released v6 of the SSPI-SASL bridge:

                               

                              Changelog:

                              v6:

                                - Free the SSPI model during finalize

                                - Only Free/Delete security buffers that have been used (NT4 fix)

                                - Made a static buffer into a member variable

                                - Assert for Privileges to add SASL methods

                                - Implement getMechanismName

                                - Now built with Java 1.6 (with -source/-target 1.5 for compatibility with Java1.5)

                               

                              So several memory leaks and threading contention issues have been removed, I haven''t checked it in my live production Wildfire envionment yet (Java1.5), but it works in my dev testing non-Wildfire/SaslCheck env (Java1.6)

                                • Re: NTLM
                                  victorae

                                  Hi!

                                   

                                  SASL-SSPI   v6.2

                                  Wildfire 3.1.1

                                  Pandion 2.5

                                  -  - work, but without windows autentification.

                                   

                                  #

                                  1. An unexpected error has been detected by HotSpot Virtual Machine:

                                  #

                                  1. EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x77fcd79a, pid=3500, tid=2796

                                  #

                                  1. Java VM: Java HotSpot(TM) Server VM (1.5.0_08-b03 mixed mode)

                                  2. Problematic frame:

                                  #

                                   

                                  -


                                    T H R E A D  -


                                   

                                  Current thread (0x2a690668):  JavaThread "Client SR - 27525703" daemon

                                    • Re: NTLM

                                      Please email me (see my profile for email address) a Dr Watson dump (see the info I posted in this thread on 23-Oct-2006, and 8-Nov-2006 on how to enable the dump switch).  Also please try the dll from the src\SaslSspi-C\Debug folder.

                                • Re: NTLM

                                  Norman, supppppper!