On 02/15/2013 02:48 PM, Zeke Evans wrote: > Thanks for the clarification and pointing me to the testing docs. One > part of your reply I don't understand -- > >> The Security Policy documents the command as "./config", not "./config >> no-asm" > > The build works without no-asm, but I don't understand how the > Security Policy does not allow "./config no-asm". I intend to build > with just "./config" but want to make sure I understand when no-asm is > and is not allowed. Appendix A specifies both. There is a note in > the User Guide about the use of no-asm depending on the platform, but > I don't see anything that suggests you can't use no-asm with SPARC.
It does get rather confusing with so many platforms. If you look at Table 2 you will see that the two SPARC platforms were tested with a "Build Method" of "U2". Then in Appendix A you will see "U1" defined as "./config no-asm ..." and "U2" defined as "./config ...". So if you want to claim your platform as directly tested for validation #1747 you'll want to match the platform description in Table 2 (the alternative is to "user affirm" the validation as applying to your slightly different platform). For some platforms there is no practical difference between "./config no-asm" and "./config", where no assembler optimizations are present, but the Security Policy instructions are meant to be taken very literally. Think of those "Build Method" commands as a magic incantation. -Steve M. -- Steve Marquess OpenSSL Software Foundation, Inc. 1829 Mount Ephraim Road Adamstown, MD 21710 USA +1 877 673 6775 s/b +1 301 874 2571 direct marqu...@opensslfoundation.com marqu...@openssl.com ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
