It is very common to misuse the openssl command-line for this due to confusion over the DigestInfo structure, see e.g. my answer here:
http://stackoverflow.com/questions/14444741/cant-get-openssl-signed-data-to-match-net-signed-data-or-bouncycastle-signed-d

If that is not clear, please give the exact openssl command line you are trying to match.

Regards,
Pete Dettman

On 27/06/2013 7:24 PM, Mankowski, Chris wrote:
I'm fairly certain it does exist in Bouncy Castle.

Do you have any more information on this bug in .net?

----- Original Message -----
From: Jean-Paul Berthelot [mailto:[email protected]]
Sent: Thursday, June 27, 2013 07:09 AM
To: [email protected] <[email protected]>
Subject: [dev-crypto-csharp] Calculate RSA SHA-256 digest value

Hi,



I have a specific problem I am trying to solve and I was wondering if Bouncy 
Castle could assist me.



I have a byte array contain an xml element and need to calculate the RSA 
SHA-256 digest value.



There is a bug in the native Microsoft SHA256Managed class that produces a 
different has to when the digest is calculated via openssl on the command line.





Does Bouncy Castle offer a class that would take a byte array and the calculate 
the RSA SHA-256 digest?



I need the algorithm to be equivalent to OpenSSL.



Could someone please advice me.



Kind regards,



Jean-Paul

**********************************************************************
Notice: This e-mail message and any attachment to this e-mail message may 
contain information that is confidential, proprietary, privileged, legally 
privileged and/or exempt from disclosure under applicable law.  If you are not 
the intended recipient, please accept this as notice that any disclosure, 
copying, distribution or use of the information contained in this transmission 
is strictly prohibited. NFP reserves the right, to the extent and under 
circumstances permitted by applicable law, to retain, monitor and intercept 
e-mail messages to and from its systems.

Any views or opinions expressed in this e-mail are those of the sender and do 
not necessarily express those of NFP.  Although this transmission and any 
attachment are believed to be free of any virus or other defect that might 
affect any computer system into which it is received and opened, it is the 
responsibility of the recipient to ensure that it is virus free and no 
responsibility is accepted by NFP, its subsidiaries and affiliates, as 
applicable, for any loss or damage arising in any way from its use.

If you have received this e-mail in error, please immediately contact the 
sender by return e-mail or by telephone at 212-301-4000 and destroy the 
material in its entirety, whether electronic or hard copy format.



Reply via email to