I just noticed this email sitting in my inbox. Have you been able to resolve this problem? If not unfortunately I don't have access to a Solaris machine with gcc 3.2.1 installed. I suggest that you run your test program under a debugger on both Solaris and Windows, and trace the executions step by step until they start to differ, and try to pin down where the problem lies.
On Tue, Apr 29, 2003 at 04:49:46PM +0300, Murat Eren wrote: > Hi, > I am using crypto51 for dsa, signing and verifying. I encountered with the problem > that same keys are validated in Windows, but not in Solaris. Attached you will find > the test program source code and keys and Makefile for Solaris. > I am using VC60 in windows, and g++ in Solaris. > > (Configured with: ../configure --disable-nls --with-as=/usr/ccs/bin/as > --with-ld=/usr/ccs/bin/ld > Thread model: posix > gcc version 3.2.1) > > Any idea? Looking forward for a solution. > > Murat :-) > > > PRIVATEKEY=3081E60201003081C806072A8648CE3804013081BC025100E75A6B0D916F9C54550A33E08883D7C1DCA709B788FC5BA9213EF57FC9108E5B82BC95E19F3B212D990F1A67E24A1A41A7152F2BEC90407893DCBB27649C338324F52E1AD55584FC6DF5851F4CBB4CD9021500BE17D64A1F3977E36A9C26F5E30B10138C560EA302503D44B008458183A14BBDDE2A24FE18251B88E7CC9A1BF8084F415E86C80C89878FCD2B7256212255862F804FBCC253CAC42C7AFFF169F8F4F5B1D46781D311BF4FC1029A9C2B536A1388AB365180E43B041602140CE332CD24E533B9EAB2134E0A0AA3B89964584B > PUBLICKEY=308201203081C806072A8648CE3804013081BC025100E75A6B0D916F9C54550A33E08883D7C1DCA709B788FC5BA9213EF57FC9108E5B82BC95E19F3B212D990F1A67E24A1A41A7152F2BEC90407893DCBB27649C338324F52E1AD55584FC6DF5851F4CBB4CD9021500BE17D64A1F3977E36A9C26F5E30B10138C560EA302503D44B008458183A14BBDDE2A24FE18251B88E7CC9A1BF8084F415E86C80C89878FCD2B7256212255862F804FBCC253CAC42C7AFFF169F8F4F5B1D46781D311BF4FC1029A9C2B536A1388AB365180E43B03530002503BC4A87B7730CB268A5A0915E06B6BC544B231422A79D6729C931694B2309D428AAD23B49600F32DF8B4054716DC48C0147049570C11C915648FC66570DD6587EC7B7F0DBC8E870D86DE8823388772E2
