[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bouncycastle-crypto-dev
Subject:    Re: [dev-crypto] Problem using smime encryption with 2 writeTo
From:       David Hook <dgh () lockboxlabs ! com>
Date:       2011-09-11 21:04:23
Message-ID: 1315775063.2261.14.camel () konkolo
[Download RAW message or body]

Sorry, somehow missed the original post.

As Martijn just hinted, the SMIME classes are built on a streaming API.
This has the advantage that you can process arbitrarily large messages,
but it does rule out doing a second writeTo.

Regards,

David

On Sat, 2011-09-10 at 09:54 +0200, Christian Anke wrote:
> Hi list,
> 
> i wonder about the fact that nobody is interested in solving this
> problem. Am i doing anything wrong? More information
> needed? Or is this a trivial problem like "everybody should know this"?
> 
> I'll be glad if anybody can help me.
> 
> 
> 
> On 23.08.2011 09:58, Carcinoma wrote:
> > Hi list,
> >
> > it seems to me, there ist a problem with smime encryption. When i use
> > the smsime encryption from bc and i tried to write the mail into an
> > outputstem using .writeTo from the Encrypted MimeMessage, the i only
> > got vaild conent on the first writeTo. The second one will only output
> > the headers but no content. Is there anything known about that
> > bahaviour? Should i avoid the second writeTo?
> >
> > I use bc 1.46.
> >
> > Greedings, carci
> >
> >
> 
> 



[prev in list] [next in list] [prev in thread] [next in thread]