> Objective also is to pinpoint the problem to specific algorithm on > specific platform. Mentioning two distinct platforms running different > versions, like SPARC running 1.0.2 and x86 0.9.8g, does not make things > clearer. You have to present evidence that directly supports given > assumption, i.e. that 1.0.2 fails on SPARC.
Or course you probably mean to say that this is evidence that SHA2 appears to be broken on SPARC. In order to make trouble-shooting more structured it's appropriate to double-check and confirm this by testing different s_client -cipher against s_server running on SPARC. Then to spare time one can drop optimization level only for affected module by manually removing corresponding .o, modifying CFLAG in top Makefile and re-running make. This way only couple of files will be recompiled so you don't have to wait for complete build (which is rather slow on SPARC). In other words, identify algorithm first, then experiment with compiler optimization levels. _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
