Hi Lukas, Cheers for the update :)
I've updated the 'ntlmmsgs' unit so it no longer uses the 'ntlmencryption' unit (using synacrypt/synacode for all crypto/coding stuff now). As a result, there are a few extra bits and pieces in the 'ntlmmsgs' unit to handle preparing the DES keys correctly. As for the OnAfterConnect - I can't see how this is useful for implementing the hacks required for NTLM authentication (as it occurs in the tunneling which happens before the hook). Maybe I'm missing the point :) Anyway.. here is a snapshot of the files working with 38b2/synacrypt.. Synapse NTLM Authentication Demos (synasnap-38b2) http://www.filesend.net/download.php?f=acfa543c230fae6d249fc713d4872619 cheers, ben Lukas Gebauer wrote: > some tips: > > Use synasnap 38b2, because: > > - synacode have MD4 (you must not use it from NTLMencryption unit) > > - synacopde have base64 routines (you must not use it from > NTLMencryption unit) > > - synacrypt have DES encryption (you must not use it from > ntlmencryption unit. So, you can omit ntlmencryption unit at all!) > > - TTCPBlockSocket have new event OnAfterConnect. So, you must not > create your own TTCPBlocksocket descendant, because all needed hacks > can be implented by this event. > > > > > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
