Re: Fwd: I-D ACTION:draft-ietf-smime-examples-09.txt
Jeff Jacoby <[email protected]> Wed, 06 Nov 2002 17:06:32 -0800
| Newsgroups | gmane.ietf.smime-examples |
|---|---|
| Organization | RSA Security, Inc. |
| Message-ID | <[email protected]> |
Blake Ramsdell wrote: > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of > > Jeff Jacoby > > Sent: Wednesday, November 06, 2002 10:25 AM > > To: Paul Hoffman / IMC > > Cc: [email protected] > > Subject: Re: Fwd: I-D ACTION:draft-ietf-smime-examples-09.txt > > > > Also, I notice there is only one message which is indefinite-length > > encoded. Will there be more examples with indefinte-length enodings? > > What cases are you concerned about? Total length of an indefininte > length block > 64K? > > Blake It could be that I'm confusing myself, or I'm just making things unnecessarily complicated, but I was thinking of a "streaming" case. By this I mean: - Lot's of data is to be signed and enveloped. The data is available only a little bit at a time, nor do I know how much there ultimately will be. - I run the data through my CMS signing routines, which most likely produce indefinite-length encodings (unless I want to buffer everything), then... - run that (indefinite-length) contentInfo through my enveloping routines. Or perhaps vice-versa (enveloping then signing). I'm just interested in making sure I'm encrypting (or signing) the correct octets of the incoming indefinite-length message. Or my coffee fix isn't working and I'm just generally confused about things and there's nothing really to worry about. :) Jeff