On Tue, 2013-02-19 at 16:48 +0000, Viktor Dukhovni wrote:
> On Tue, Feb 19, 2013 at 03:57:00AM -0500, Nick wrote:
> 
> > I see EVP_EncodeUpdate adds a newline char after every 64 chars of
> > output (presumably to wrap the output).  Can this be disabled?
> 
> No, but the EVP_EncodeBlock() function does not generate any newlines.
> You must pass it a multiple of 3-bytes on every call except the last,
> since it will otherwise generate trailing "=" padding for incomplete
> blocks, which are not valid midstream.
> 
> Another option is to roll your own Base64 encoder, this is trivial
> to implement, there is little incentive to use the EVP routines if
> they don't do exactly what you want.
> 

Thanks.  I've implemented a base64 codec in the past w/out a problem.
But I figured if there was an easy way to get my desired functionality
from an existing & tested API, all the better.  As it turns out, the
wrapping does not seem to be an issue afterall--the consuming app
handles it fine.


Nick


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [email protected]
Automated List Manager                           [email protected]

Reply via email to