On 09/03/2015 03:26 PM, Rich Salz wrote: > The branch master has been updated > via 64b25758edca688a30f02c260262150f7ad0bc7d (commit) > from fb4844bbc62fb014c115cd8fd2fc4304cba6eb89 (commit) > > > - Log ----------------------------------------------------------------- > commit 64b25758edca688a30f02c260262150f7ad0bc7d > Author: Rich Salz <rs...@akamai.com> > Date: Thu Sep 3 09:15:26 2015 -0400 > > remove 0 assignments. > > After openssl_zalloc, cleanup more "set to 0/NULL" assignments. > Many are from github feedback.
Interestingly, Viktor had just added some explicit NULL assignments after memset-to-zero a few days ago in a0724ef1c9b9e2090bdd96b784f492b6a3952957. It is permitted for the NULL pointer to have a representation other than all-zeros, but such platforms are rare, and are explicitly excluded from the supported platforms list for, e.g., MIT krb5. Does openssl want to try to support such platforms? -Ben _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
