| [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "Bryan" == Bryan Hoover <bhoover@xxxxxxxx> writes: Bryan> One small thing -- I noticed a change in the SRPClient password Bryan> initialization so that it expects the password property to Bryan> contain a char[] array rather than a Password object, as I had Bryan> put it. I was wondering what your thinking was on that. Bryan> Either way -- whether change to char[] or Password, from String Bryan> -- from the gnu-crypto lib client perspective, api interfacing Bryan> would need to be changed anyway (short of some other api work Bryan> around, or addition). When I was merging your patches I mistakenly thought that SaslClient had to expect a char[] array, as a part of the SASL API. I don't think it does, however, so using a Password object is fine. Actually, it would be better to be able to gracefully handle either a char[] or a Password. My mistake; I'll fix this now. - -- Casey Marshall || csm@xxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQFAlFG+gAuWMgRGsWsRAuABAJ98Yb1bcmpqMhNma/rdSh/qWMd0qACfUQyv hlNZbKkSmfHEeIJMYf2brn8= =E5t2 -----END PGP SIGNATURE----- _______________________________________________ gnu-crypto-discuss mailing list gnu-crypto-discuss@xxxxxxx http://mail.nongnu.org/mailman/listinfo/gnu-crypto-discuss
[Home] [Gnu Classpath] [Linux Kernel] [Linux Cryptography] [Fedora] [Fedora Directory] [Red Hat Development] [Red Hat 9 Bible] [Fedora Bible] [Red Hat 9] [Network Security Reading]
|