Re: [GNU Crypto] exception on multiple SaslConnection.send() calls

[Jim Basney]

Bryan Hoover <address@hidden> wrote:
> Jim Basney wrote:
> 
> > Bryan Hoover <address@hidden> wrote:
> > > Jim Basney wrote:
> > > > Am I doing something wrong?
> > >
> > > Don't comment the reconnect call :).  If possible, the existing 
> > > connection will be reused,
> > > so "reconnect" is in a sense, a bit of a misnomer.
> >
> > Hmmm.  SaslConnection.reconnect() calls disconnect() then connect(),
> > which creates a new Socket().  Watching the network with ngrep, I see a
> > new TCP socket connection after the SaslConnection.reconnect() call.
> 
> Well, statelessness protocals, and all that you know.
> 
> But the security session -- that's the time consuming thing you want to reuse 
> if possible, and
> that what the lib does, unless, for instance, it's been to long, and session 
> timed out.  Then
> you have to renogotiate the security layer -- basically start all over like a 
> first time
> connection.

You're saying that I can only call SaslClient.wrap() once, after which I
have to go through the SaslClient.evaluateChallenge() loop again?

-Jim