You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by Soren Hilmer <so...@tietoenator.com> on 2005/09/08 09:38:01 UTC
Fwd: [dev-crypto] warning about JavaMail 1.3.3
Just saw this on the BouncyCastle mailinglist, as we provide mailets using
BouncyCastle we should perhaps revise upgrading to JavaMail 1.3.3.
--Søren
---------- Forwarded Message ----------
Subject: [dev-crypto] warning about JavaMail 1.3.3
Date: Thursday 08 September 2005 00:25
From: David Hook <dg...@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.
Regards,
David
-------------------------------------------------------
--
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
Re: [dev-crypto] warning about JavaMail 1.3.3
Posted by Stefano Bagnara <ap...@bago.org>.
> So our main reason is the performance improvement in base64
> handling, and this is exactly what seams broken. So I suggest
> reverting to JavaMail 1.3.2 until a bugfix-release from Sun
> is available.
I reopened the JIRA issue so we know that there is a possible problem. We
better should downgrade if no solution will be provided before our release.
Unfortunately I can't see bug reports against javamail 1.3.3 on
java.sun.com.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
Re: [dev-crypto] warning about JavaMail 1.3.3
Posted by Soren Hilmer <so...@tietoenator.com>.
Well good questions, I read your entry on the upgrade, wher you state:
"Probably only performance improvement on base64 encoding/decoding.
Most of the other changes are around IMAP (client) and we don't use it. "
So our main reason is the performance improvement in base64 handling, and this
is exactly what seams broken. So I suggest reverting to JavaMail 1.3.2 until
a bugfix-release from Sun is available.
--Søren
On Thursday 08 September 2005 11:25, Stefano Bagnara wrote:
> > Just saw this on the BouncyCastle mailinglist, as we provide
> > mailets using BouncyCastle we should perhaps revise upgrading
> > to JavaMail 1.3.3.
> >
> > --Søren
>
> Hi Søren,
>
> Thank you for pointing this out. What should we do?
> I haven't tested S/MIME stuff since the upgrade to javamail 1.3.3.
> Should I revert the upgrade to mail-1.3.3? Should we add a FAQ?
> Should we add a note in the config.xml just before the SMIME stuff?
>
> Stefano
>
> > Subject: [dev-crypto] warning about JavaMail 1.3.3
> > Date: Thursday 08 September 2005 00:25
> > From: David Hook <dg...@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.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
--
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
Re: [dev-crypto] warning about JavaMail 1.3.3
Posted by Stefano Bagnara <ap...@bago.org>.
> Just saw this on the BouncyCastle mailinglist, as we provide
> mailets using BouncyCastle we should perhaps revise upgrading
> to JavaMail 1.3.3.
>
> --Søren
Hi Søren,
Thank you for pointing this out. What should we do?
I haven't tested S/MIME stuff since the upgrade to javamail 1.3.3.
Should I revert the upgrade to mail-1.3.3? Should we add a FAQ?
Should we add a note in the config.xml just before the SMIME stuff?
Stefano
> Subject: [dev-crypto] warning about JavaMail 1.3.3
> Date: Thursday 08 September 2005 00:25
> From: David Hook <dg...@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.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org