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

[Bryan Hoover]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bryan Hoover wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jim Basney wrote:
>
> > Hello,
> >
> > I see that SaslC.java calls SaslConnection.reconnect() between two calls
> > to SaslConnection.send().  Is it not possible to send multiple messages
> > on the same SaslConnection?  If I comment the SaslConnection.reconnect()
> > call in SaslC.java and add a corresponding second receive() call in
> > SaslS.java, I get the following exceptions:
> >
> > ----------
> >     [saslc] [SaslConnection] Connected!
> >     [saslc] [SaslConnection] Outgoing message (str): There is more than one 
> > way to do it
> >     [saslc] [SaslConnection] Incoming response (str): ok
> >     [saslc] [SaslConnection] Outgoing message (str): 1 if by land. 2 if by 
> > sea...
> >     [saslc] java.lang.IllegalStateException
> >     [saslc]     at 
> > gnu.crypto.assembly.Assembly.lastUpdate(Assembly.java:267)
> >     [saslc]     at gnu.crypto.sasl.srp.CALG.doFinal(CALG.java:270)
> >     [saslc]     at 
> > gnu.crypto.sasl.srp.SRPClient.engineWrap(SRPClient.java:328)
> >     [saslc]     at 
> > gnu.crypto.sasl.ClientMechanism.wrap(ClientMechanism.java:136)
> >     [saslc]     at 
> > gnu.crypto.sasl.SaslOutputStream.write(SaslOutputStream.java:168)
> >     [saslc]     at java.io.OutputStream.write(OutputStream.java:58)
> >     [saslc]     at 
> > gnu.crypto.tool.SaslConnection.send(SaslConnection.java:244)
> >     [saslc]     at gnu.crypto.tool.SaslC.run(SaslC.java:148)
> >     [saslc]     at java.lang.Thread.run(Thread.java:552)
> >     [saslc] Client C0 shutdown...
> >     [saslc] Exiting...
> > ----------
> >     [sasls] ************** Connection authenticated....
> >     [sasls] Incoming request (str): There is more than one way to do it
> >     [sasls] Outgoing message (str): ok
> >     [sasls] Incoming request (str): ÿ
> >     [sasls] Outgoing message (str): ok
> >     [sasls] Exception while processing connection
> >     [sasls] Connection shutdown...
> >     [sasls] java.lang.IllegalStateException
> >     [sasls]     at 
> > gnu.crypto.assembly.Assembly.lastUpdate(Assembly.java:267)
> >     [sasls]     at gnu.crypto.sasl.srp.CALG.doFinal(CALG.java:270)
> >     [sasls]     at 
> > gnu.crypto.sasl.srp.SRPServer.engineWrap(SRPServer.java:363)
> >     [sasls]     at 
> > gnu.crypto.sasl.ServerMechanism.wrap(ServerMechanism.java:139)
> >     [sasls]     at 
> > gnu.crypto.sasl.SaslOutputStream.write(SaslOutputStream.java:170)
> >     [sasls]     at java.io.OutputStream.write(OutputStream.java:58)
> >     [sasls]     at gnu.crypto.tool.SaslS.send(SaslS.java:328)
> >     [sasls]     at gnu.crypto.tool.SaslS.run(SaslS.java:291)
> >     [sasls]     at java.lang.Thread.run(Thread.java:552)
> > ----------
> >
> > 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.

And come to think of it, the connection, and the security layer session are two 
different
things.  So, reconnect isn't so much a misnomer after all.  You reconnect, but 
you reuse, if
possible, the security session -- don't have to go through renogotiating and 
all that.

Bryan

> Bryan
>
> > -Jim
> >
> > _______________________________________________
> > gnu-crypto-discuss mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/gnu-crypto-discuss
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (MingW32) - GPGrelay v0.955
>
> iD8DBQFBt5G+38ZFbCo67y4RAuvcAJ9JYA6ONepw2MPQ8PQrlMQcM+YSxACeMcXu
> 6plAeuAFCEfFB74wp32cKk4=
> =3U8d
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> gnu-crypto-discuss mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnu-crypto-discuss

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32) - GPGrelay v0.955

iD8DBQFBt5OD38ZFbCo67y4RApmoAJ9oxkN79smdZHNUTSq/YNUYPWbU8wCdG7uN
ha11rdFPhZlg2BHjjDcnCP0=
=m+d1
-----END PGP SIGNATURE-----