Run-time checking works for x86, but not for arm (OPENSSL_armcap_P is hidden, I still have to try over environment variables, which are not as flexible for arm as for x86).
Anyway, it would be helpful to exclude hardware aes instructions at compile-time: 1) Runtime checking is error prone (openssl and code using openssl evolve) 2) Proving to a customer (or convincing myself) that no such instructions will ever be used is much easier if such instructions are not even compiled I guess that some of the already existing no-xxx configuration options have been introduced for similar reasons. ________________________________ From: Rich Salz via RT <r...@openssl.org> Sent: Thursday, June 16, 2016 8:15:48 PM To: Loic Etienne Cc: openssl-dev@openssl.org Subject: [openssl.org #4570] Enhancement request: Configuration option no-hw-aes On Tue Jun 14 15:43:26 2016, loic.etie...@qnective.com wrote: > Define a configuration option no-hw-aes. > No aes processor instruction should be compiled if one of the > configuration options no-hw or no-hw-aes is given. Why doesn't existing run-time checking work for you? -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4570 Please log in as guest with password guest if prompted -- Ticket here: http://rt.openssl.org/Ticket/Display.html?id=4570 Please log in as guest with password guest if prompted -- openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
