On Oct 5, 2011, at 9:10 PM, William A. Rowe Jr. wrote:
> On 10/5/2011 10:08 AM, Dr. Stephen Henson wrote:
>> On Tue, Oct 04, 2011, William A. Rowe Jr. wrote:
>>
>>> On 10/4/2011 10:45 PM, Bill Durant wrote:
But when I run it under Windows NT, I get the following run-time error:
>>
On 10/5/2011 10:08 AM, Dr. Stephen Henson wrote:
> On Tue, Oct 04, 2011, William A. Rowe Jr. wrote:
>
>> On 10/4/2011 10:45 PM, Bill Durant wrote:
>>>
>>> But when I run it under Windows NT, I get the following run-time error:
>>>
>>> "The procedure entry point Module32NextW could not be locat
On Wed, Oct 05, 2011, Bill Durant wrote:
> On Oct 5, 2011, at 8:08 AM, Dr. Stephen Henson wrote:
> > On Tue, Oct 04, 2011, William A. Rowe Jr. wrote:
> >
> >> On 10/4/2011 10:45 PM, Bill Durant wrote:
> >>>
> >>> Does anyone know how to produce a FIPS-capable OpenSSL that works on
> >>> Windows
On Oct 5, 2011, at 8:08 AM, Dr. Stephen Henson wrote:
> On Tue, Oct 04, 2011, William A. Rowe Jr. wrote:
>
>> On 10/4/2011 10:45 PM, Bill Durant wrote:
>>>
>>> Does anyone know how to produce a FIPS-capable OpenSSL that works on
>>> Windows NT?
>>
>> It's likely not possible...
>>
>>> But when
On Tue, Oct 04, 2011, William A. Rowe Jr. wrote:
> On 10/4/2011 10:45 PM, Bill Durant wrote:
> >
> > Does anyone know how to produce a FIPS-capable OpenSSL that works on
> > Windows NT?
>
> It's likely not possible...
>
> > But when I run it under Windows NT, I get the following run-time error
On Tue October 4 2011, William A. Rowe Jr. wrote:
> On 10/4/2011 10:45 PM, Bill Durant wrote:
> >
> > Does anyone know how to produce a FIPS-capable OpenSSL that works on
> > Windows NT?
>
> It's likely not possible...
>
> > But when I run it under Windows NT, I get the following run-time error
On 10/5/2011 6:59 AM, William A. Rowe Jr. wrote:
On 10/4/2011 10:45 PM, Bill Durant wrote:
Does anyone know how to produce a FIPS-capable OpenSSL that works on Windows NT?
It's likely not possible...
But when I run it under Windows NT, I get the following run-time error:
"The procedu
On 10/5/2011 8:15 AM, brajan wrote:
My steps are
1. raw data eg.balamurugan
2. i am calculating hash for this data using sha256 which is 256 bit for
readable i convert this into (32 to 64 byte) hex string not hex represent.
eg hash string is a123sdf... which is 64 characters
3. now i am gi