[jcifs] Re: OutOfBounds exception in authenticate

[erez]

Asaf Mesika <asaf.mesika <at> gmail.com> writes:

> 
> 
> What version are you using of jCIFS?I recall encountering a similiar bug which
was solved in some version.
> On Fri, May 1, 2009 at 12:48 PM, erez <erez_levav <at> newyorklife.com> wrote:
> Michael B Allen <ioplex <at> gmail.com> writes:
> >
> 
> > On Thu, Apr 30, 2009 at 3:35 PM, erez
> 
> <erez_levav <at> newyorklife.com> wrote:
> > > Michael B Allen <ioplex <at> gmail.com> writes:
> > >
> 
> > I don't know. But if you send me a packet capture I can very quickly
> > see if it's doing NTLMv2.
> >
> > Mike
> >
> I think I got it... well, this looks like a capture of somen' ;))))
> javax.net.ssl.trustStore=/prod/sys/WebSphere/AppServer6/profiles/ap00d04
> etc/DummyServerTrustFile.jks
> javax.net.ssl.keyStorePassword=WebAS
> [5/1/09 11:34:25:581 EDT] 00000060 SystemErr  R
> SmbComNegotiate[command=SMB_COM_NEGOTIATE,received=false,errorCode=0,
> flags=0x0018,flags2=0xC803,signSeq=0,tid=0,pid=876,uid=0,mid=1,
> wordCount=0,byteCount=12,wordCount=0,dialects=NT LM 0.12]
> [5/1/09 11:34:25:583 EDT] 00000060 SystemErr  R New data read:
> Transport1[ny-somename.nt.newyorklife.com/168.28.173.16:0]
> [5/1/09 11:34:25:584 EDT] 00000060 SystemErrR 00000: FF 53 4D 42 72 00 00
> 00 00 98 03 C8 00 00 00 00  |ÿSMBr......È....|
> 00010: 00 00 00 00 00 00 00 00 00 00 6C 03 00 00 01 00  |..........l.....|
> [5/1/09 11:34:25:585 EDT] 00000060 SystemErr     R
> [5/1/09 11:34:25:586 EDT] 00000060 SystemErr     R
> SmbComNegotiateResponse[command=SMB_COM_NEGOTIATE,received=false,
> errorCode=0,flags=0x0098,flags2=0xC803,signSeq=0,tid=0,pid=876,
> uid=0,mid=1,wordCount=17,byteCount=124,wordCount=17,dialectIndex=0,
> securityMode=0x7,security=userencryptedPasswords=true,maxMpxCount=50,
> maxNumberVcs=1,maxBufferSize=16644,maxRawSize=65536,
> sessionKey=0x00000000,capabilities=0x8001F3FD,
> serverTime=Friday 01 11:34:25 EDT 2009,
> serverTimeZone=240,encryptionKeyLength=0,byteCount=124, oemDomainName=]
> 
> 
> 
> 

Interesting observation -- you see...  Since my code USED to work, I
rolled back to my last known working set.  (re)deployed, and -- *still*
not working!  So, I decided to go back to an older JCIFS jar.  In fact,
a version I knew worked -- 1.2.25b.  Low and behold, that worked!!!
Now I'm going to re-re-deploy my new code and test.  But you are absolutely
correct -- it is jar version dependent.  So the JARs that didn't work (so far)
are 1.3.2 and 1.3.8.  I will have to painfully try each of the interim JARs
to see where it breaks.  Unless, there is a new configuration parameter
that I'm not aware of there must be a bug in there, right?

Thanks.