On Fri, Mar 18, 2016 at 9:46 PM, Richard Levitte via RT <r...@openssl.org> wrote: > In this case, though, it's an application that explicitely calls an > aborting function. No subterfuge at all there, so if you wanted to > complain, this is a particularly bad example. > > We do use OPENSSL_assert() in some places, to check *internal* state. > When internal state is incorrect, it's not something that should keep > running. The aim is, of course, that such errors will be caught by > our tests.
When the library aborts, what keeps sensitive information from being written to disk and then sent to Apple, Microsoft, <favorite distro> in a crash report? Jeff -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
