> >> My apologies for asking. I don't have access to Solaris at the moment, >> and the Solaris machines at the GCC compile farm are down. >> > > Acess to solaris is not that tricky for projects that desire to support > it. Being a freelancer I have my own solaris machine, which I occasionally > use for client work. I got it on ebay for 200 pounds. What is slightly > trickier is getting access to the proprietary sun compiler. I haven't > managed to do that so I use gcc on my own solaris machine. That's no good > for tackling this problem since the issue seems to be related to the > compiler. >
The Sun compilers are notorious at times. I've been nervous about them since we lost access to them. I think we have been skirting by, but its no way to approach Security Testing and Evaluation. On a side note, Peter Guttman, who is the author of Cryptlib (http://www.cs.auckland.ac.nz/~pgut001/cryptlib/), once quipped (http://permalink.gmane.org/gmane.comp.encryption.cryptlib/2836): ... vendors have traditionally shipped truly ghastly C compilers (or, in Sun's case, a non-C compiler that pretended to be a compiler so you had to use all sorts of trickery to determine whether there was a real compiler present or not) ... Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
