james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Soren Hilmer <soren.hil...@tietoenator.com>
Subject Fwd: [dev-crypto] warning about JavaMail 1.3.3
Date Thu, 08 Sep 2005 07:38:01 GMT
Just saw this on the BouncyCastle mailinglist, as we provide mailets using 
BouncyCastle we should perhaps revise upgrading to JavaMail 1.3.3.


----------  Forwarded Message  ----------

Subject: [dev-crypto] warning about JavaMail 1.3.3
Date: Thursday 08 September 2005 00:25
From: David Hook <dgh@bund.com.au>
To: dev-crypto@bouncycastle.org

We're not sure exactly what's happening still, but it appears that on
some platforms, under some circumstances, Base64 decoding, or something
underlying it, in JavaMail 1.3.3 breaks horribly and produces data with
lots of extra bytes of the value 0x00 and 0xff. The upshot of this is
that messages containing Base64 encoded data, such as S/MIME messages
will no longer work as the data stream containing the encoded message
has become corrupted.

If S/MIME starts causing exceptions we recommend moving back to 1.3.2.




Søren Hilmer, M.Sc.
R&D manager		Phone:	+45 72 30 64 00
TietoEnator IT+ A/S	Fax:	+45 72 30 64 02
Ved Lunden 12		Direct:	+45 72 30 64 57
DK-8230 Åbyhøj		Email:	soren.hilmer <at> tietoenator.com

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message