That doesn't sound like an ideal case for a bugfix. Any other creative ideas on how to fix this one? Some suggestions I read previously included adding support for streaming decode to avoid such a large memory allocation. This may not easily be feasible because of needing to verify signatures on the message.
If not, I'll try out the size_t change. On Wed, Aug 17, 2016 at 2:02 PM, Salz, Rich via RT <r...@openssl.org> wrote: > Try it, it will be a huge invasive change. > > > -- > Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4651 > Please log in as guest with password guest if prompted > > -- Brian Morton Morton Software Insights 404-667-1095 bmor...@mortoninsights.com <https://mortonsoftwareinsights.freshbooks.com/> -- 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
