This would be extremely useful for the UEFI build too. For us it's not the insanely-tinfoil-hat concern about revealing "private" information about which directory OpenSSL happens to have been built in; it's more about the need to have *small* and *reproducible* builds.
EDK II currently carries a big patch which just takes the brute-force approach of replacing all instances of __FILE__ with NULL, and __LINE__ with 0. Rather than littering the source with #ifdef NDEBUG, I had considered instead introducing OPENSSL_FILE and OPENSSL_LINE. I think those would do the right thing in situ, rather than picking up the filename and line on which OPENSSL_FILE and OPENSSL_LINE respectively were defined? Perhaps it could be just depend on OPENSSL_SMALL_FOOTPRINT? -- David Woodhouse Open Source Technology Centre david.woodho...@intel.com Intel Corporation _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
