With the talk of a release, I'd note that the Java Base64 encoder in the
utility class is still adding an extra linefeed when the encoded data ends
up exactly on a line wrap boundary (e.g. last line of 72 chars if wrap
length is 72).
This is treated as invalid by the Xerces C++ base64 data type validator. I
don't know what purpose the extra linefeed serves, but I think it should
be removed. It causes problems that really can't be avoided easily, since
whatever wrap value you pick could be matched by *some* certificate.
I remember the bug and I will look into it today..
What are the thoughts on the list of using jakarta-commons-codec?
We can either take the entire library and use it as a library or could just rip out the needed classes and package those.
I like the rip-out-and-use idea. Less dependencies. That is, if it works... ;-)
+1 - rip-out.
Ax/
Erwin
smime.p7s
Description: S/MIME Cryptographic Signature
