Problem with cms signer and sha256 digest algorithm and etoken on window 7 sp1

Question

0.00/5 (No votes)

See more:

hi all,

I am trying to sign my data by using cms signer and sha256 digest algo .

code is working fine on my machine .

but on client machine i am getting internal server error

can any one have any idea please share

it is little bit urgent .

thanks

What I have tried:

CmsSigner signer = new CmsSigner(certificate);

signer.DigestAlgorithm = new Oid("SHA256");// ("2.16.840.1.101.3.4.2.1");
signer.SignedAttributes.Add(new Pkcs9SigningTime());
// create the signature
signer.IncludeOption = X509IncludeOption.None;

signedCms.ComputeSignature(signer, false);

Posted 1-Jun-16 4:08am

gourav agrawal

Updated 1-Jun-16 6:40am

Add a Solution

Comments

Richard Deeming 1-Jun-16 11:29am

"Internal server error" is just a message telling you that something went wrong; you'll need to track down the real error to find out what the problem is.

Assuming this is ASP.NET, there should be an entry in the application event log with more details. Alternatively, use Failed Request Tracing[^] to trace the failed request.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2016-06-01T06:40:00

It's exploding probably because "SHA256" is not proper Oid descriptor.

It should be:

signer.DigestAlgorithm = new Oid("2.16.840.1.101.3.4.2.1");

An "Internal server error" means that you haven't properly setup the objects and/or properties required to use the Signer. There's probably more that's wrong but you're not showing enough code to make that determination.