On Thu Aug 18 00:40:21 2016, bmor...@mortoninsights.com wrote: > > Regardless of input size (2GB or 30GB) to the smime application, the > resulting encrypted file is only 1.9GB on disk. Unless smime format > has > some very serious compression, it looks like it is silently truncating > input. A 32 bit integer dependency in the read buffer might explain > that. > Is it related, or should I file that separately? >
That's strange. It shouldn't do that. The encoding operations should work with (almost) arbitrary size input when streaming as there is no int dependency and no need to hold the complete structure in memory. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4651 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev