[jcifs] Exception in jcifs.smb.SigningDigest
Brian Moran
brianmo at yahoo.com
Tue Jun 28 20:33:13 GMT 2005
Hi, I'm using jetty-5.1.4, hosting the default example
applications, with jcifs_1.1.10's HttpNtlmAuth
filter... I have successfully "protected" everything
on my internal demo site when attempting to browse
from IE or from FireFox (prompts for dialog box when
necessary to get credentials, etc, logs in and
provides the pages).
However, when I use the Jakarta Commons HttpClient
libraries (3.0rc3), I get the following crash in
jcifs:
javax.servlet.error.message:
javax.servlet.error.exception:
jcifs.smb.SmbException:
java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at jcifs.smb.SigningDigest.(SigningDigest.java:42)
at
jcifs.smb.SmbSession.sessionSetup(SmbSession.java:267)
at jcifs.smb.SmbSession.send(SmbSession.java:228)
at jcifs.smb.SmbTree.treeConnect(SmbTree.java:134)
at jcifs.smb.SmbSession.logon(SmbSession.java:159)
at jcifs.smb.SmbSession.logon(SmbSession.java:152)
at
jcifs.http.NtlmHttpFilter.doFilter(NtlmHttpFilter.java:155)
at
org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:823)
at
org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:473)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1565)
at
org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:635)
at
org.mortbay.http.HttpContext.handle(HttpContext.java:1517)
at
org.mortbay.http.HttpServer.service(HttpServer.java:954)
at
org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
at
org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:981)
at
org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
at
org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
at
org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
at
org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Is this a known issue?
UPGRADING to 1.2.0, I get a "FAILED VALIDATE DC"
(without changing any of the jcifs.* params), but I
suspect that that is some other issue...
More information about the jcifs
mailing list