On Mon, Apr 25, 2016 at 05:45:05PM +0000, Salz, Rich wrote: > After a "set0" call, set your pointer to NULL, it's no longer yours :)
That half of the ruleset. The other half is: You must "own" any object passed to a set0 call that takes ownership of its argument (we have a few that don't take ownership, perhaps they should be renamed to just "set"). In particular, objects obtained via "get0" calls MUST NOT then be used in "set0" calls that expect to take ownership of the argument. Hdd OpenSSL been written in Rust we'd be able to make all this explicit, and have the compiler enforce the rules. That's of course impractical, we provide a C API to other C applications and libraries. -- Viktor. -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev