Why is the validity of my digitally signed document displayed as unknown?

Why is the validity of my digitally signed document displayed as unknown?
Adobe X version 10 1.4
What exactly do I have to do under Preferences-Windows Integration?

Hi amyemia,
The signer's identity is unknown because it has not been included in the list of trusted identities and none or its parent certificates are trusted identities" indicates your recipients needs to add something to their copy of Acrobat/Reader. What the recipient of the document is missing is a certificate and only you can provide him with a copy of the certificate you created to sign the PDF. After you send him or make available a copy of the certificate, then he will need to import that certificate into his copy of Acrobat
Please refer : http://helpx.adobe.com/acrobat/kb/validity-digital-signature-displayed-unknown.html
If you want your PDF signature to be valid on your / co-worker's computer, you need to supply them with your Public certificate. To do this you need to export it out as an .fdf file, if in Acrobat X, choose Edit – Protection – Security Settings, select your ID that you used to sign the PDF with and choose Export, you can then either save it to disk, or directly email your certificate, get your co-worker to double click it in Adobe Reader and follow the prompt, when you see Set Contact Trust, select it and check Use Certificate as Trusted Root. Then click OK. Now open the PDF and it should now be valid.

Similar Messages

Installed both 10.1.4 and 11.0.08 updates this week and now I can't use the Digital "Sign" document feature. It's been completely removed. Need it back. Please help..

I installed both 10.1.4 and 11.0.08 updates this week and now I can't use the Digital "Sign" document feature. It's been completely removed. Need it back. Please help.. Can't sign or add text to any pdf document. Even when security properties allow it.

I would remove Reader and repair or reinstall Acrobat.
Having different major versions can cause some users issues. Reader is not necessary if one has Acrobat installed. Even though Adobe has improved the capability of having both Reader and Acrobat with the same major version level there are still user configurations that have problems with this setup.

Update 9.1.2 breaks digital signing documents in Adobe 9 Pro on Windows XP

I am able to digitally sign documents using an Aladdin eToken Pro 64k with a fresh copy of Adobe 9 Pro for Windows. However when I update to version 9.1.2 digital signing fails with an "error encountered while BER decoding". Signing still works on Vista and Adobe 9.1.2 Pro. I've checked to make sure none of the settings relating to digital signing changed during the update and none have. Anyone have any ideas on how to correct the problem?

Hi Nick,
First up, there was a small error in my previous post. I said the version of Acrobat (and whenever I say Acrobat I really mean both Acrobat and Reader, but I'm too lazy to type both) that was modified to fix the bug in SHA-1 fallback was 9.1.3, but I really meant 9.3. Sorry about that.
I saw your post from yesterday (http://forums.adobe.com/thread/563601) where you broached the BER decoding error, but in the post above you said signature creation isn't failing any more, so hopefully some update has fixed the problem.
Here's a little bit about the BER Decoding error. During the signing process Acrobat writes the entire file to disk (which is why you always get the Save As dialog as part of the signing process) in the signed state with everything but the actual signature. However, it does leave a hole in the file where the BER encoded cryptographic data will reside once it's be computed and formatted. One thing that is created before the actual signature is the signature appearance. The signature appearance in the form field isn't really the signature proper, but just a graphic representation of the actual signature. The reason that the signature appearance is written to disk before the signature is created is because it too is part of the signed data and must exist before the actual signature is created.
In a perfect world, after the file is written to disk, the cryptographic signature is created and written into the hole in the PDF file, and the signing process completes without any problem. However, if we get to the point that the file has been written out, but during the actual signature creation the process fails, that hole I mentioned isn't filled in. It's not really a hole per se, but a block of zeros that act as a placeholder for the BER encoded data. Because there was some sort of failure and Acrobat didn't get the signed data back from the hardware device what you end up with is a PDF file with a signature appearance, but no real signature in the file. When you click on the signature field Acrobat tries to validate the actual signature, it finds the block of zeros where the signed data was supposed to be, it tries to decode the zeros and gets (as you might well imagine) nothing back and displays the BER Decoding error.
Let leaves us with why didn't Acrobat get the signed data back. When using hardware devices, such as tokens or smart cards, the actual cryptographic signing (the encryption of of the digest with the users private key) takes place on the device. Acrobat (nor any other application) doesn't have access to the private key, which is what makes hardware devices more secure. It's up to the device to sign the data and send it back. If there is any kind of breakdown in that communication channel (which I mentioned in my previous post) the signature creation doesn't reach fruition and you're left with an unsigned file that looks like it was signed because there is a signature appearance.
This is a case where we are providing technically correct, and utterly useless information. It's true that we can't decode a bunch of zeros, but what we should be telling the user is there is no signature (it's kind of like the Matrix where there is no spoon ).
I hope this helps explain what you're seeing. If the the signing process breaks down again please make sure you are using the latest version of Acrobat/Reader and the token software is up-to-date. If everything is current and the problem returns please let me know.
Steve

Printing Digitally Signed Documents

I need to be able to print digitally signed documents and would like to know if there is a way to restrict the ability to print the documents that have invalidated digital signatures. Essentially, I want to be able to email a document for remote printing and only allow the document to be printed if the digital signature is valid. It would be of additional value to me if there was a way to place a "voided" watermark across the document if the digital signature was invalid. Any thoughts or suggestions would be greatly appreciated.

Thank you.
Is there a tutorial online that would show me how I can do this?
Process Description:
1) Create pdf document from AutoCAD. I generally am required to create one pdf file per drawing sheet so I may have 100 pdf files that I am working with.
2) Assign an RM policy to each file (Could this be a batch process since I may have 100 files I am working with) that would revoke the file if the digital signature was invalid.

Password protecting digitally signed documents in Adobe Acrobat X Pro

I am looking for the combination of steps to get my digitally signed documents to be password protected for secure distribution. My documents contain new "user password" information and a number of "areas" which require digital signatures to be added.
Any input as to how one would construct a document with :
one to three --> digitally signed signatures fields in one document
Password "opening" protection for the document containing the fields; both signatures and sensitive data fields
suggestions on how to make the document open to accepting more signatures without it demanding the creation of a newly saved document after being digitally signed by one signature
I have worked at this a couple of different ways but am having problems finding the right combination/sequence of steps to make it all come together.
Please assist.....
Thanks....

......meaning.......
I can't do locking of the printing or editing of the sheet after i have encrypted and signed it. Trying to do so, wipes out out signatures. Yes, it is a great fullproof to have people be unable to change something someone has signed but if there is an ammendment, can't the creator reserve that right and in an automated sense notify the signers of the rights of the author ?
Maybe I am looking for too much but, it would be great to know if that is the reality of the whole event.
Thanks,
Robert

Stringing a number of Digitally signed documents together

Hi, I am currently running a project to convert my companies hard copy documentation packs to fully electronic, digitally signed documents.
The final document will be a string of several digitally signed documents combined together in one final document for presentation to our customers. I am currently having diffuculty retaining the original digital signature of the documents when they are combined.
I am using Acrobat Pro XI and have tried Certifying and just digitally signing but the original signatures appear to be deleted in the final document.
The real world application will be the initial company signing their docs for authentication and email it to their customer, this company will add docs to this first file and sign it then forward this on to their customer, etc until it reaches me when the completed document file will be locked.
Can anyone point me in the right direction?

Thanks, I finally worked it out. However, it's not an ideal format for how I originally visualised the outcome. From what I have read on the Adobe site and the discussion threads it doesn't appear that you can combine several digitally signed documents together to make a single document pack.
I had hoped that there was some way to have, say, 3 documents digitally signed by different people then merge these together into a single document but still retaining their individual signature details. This final document could then be certified by myself as the final recipient.
This final document pack could then be added to the final customers portfolio with many other documents.
The only way i can see to do this at the moment is to "sign" the documents with an annotation (ie. a JPG or PDF stamp), or use the built in stamps in COMMENTS, combine these into a single document and then digitally sign / certify this completed pack.
Has any one encountered this situation before and managed to solve it?
I understand that, because a change has been made to the original document this nullifies the orignal digital signature. I could live with this as long as I could retain the signatories details on that document.

How can I apply page watermarks to digitally signed documents

When printing a digitally signed PDF I need to apply a watermark across each page that states the hardcopy is an uncontrolled version of the document. I understand how to allow updates to specific form fields after the document has been signed, but cannot find a way to allow the application, removal, or modification of page level watermarks after the document has been signed.

I do not want to invalidate the digital signature when applying a watermark.
The use case is when a user prints a hardcopy of a digitally signed SOP, a watermark needs to be placed on the page that states the hardcopy is an un-controlled document, the print date, and an expiration date.
I realize that any change to a digitally signed document is normally considered to be an operation that invalidates the signatures. However, it is possible to specify fields that may be changed AFTER the signatures are applied without invalidating the signature. I am looking for the same capablity with watermarks.

Can no longer digitally sign documents

We have been using Active Directory based cetificates to digitally sign adobe pdfs for years. All of sudden after some recent updates we can no longer sign documents. When you click on a signature field and click "sign" on the pop up box, nothing happens (no error, no nothing) and pop up box stays there. I have checked and the certifcate is still valid and trusted. Everything seems to be valid. This is happening with clients that have Adobe x and Adobe 9 Reader. I tried to go back in to Adobe Professional 9.5 and certify the document but the same thing happens there! I simply can not sign anything. I have confirmed that this is an issue on other computers in our domain as well. Without an error or something else to go on, I am at a loss on how to troubleshoot. Our certificate authority is a 2008 R2 box and the clients are Windows 7.

Support information has a value as long as the product is supported. I believe Adobe ended Acrobat 9 support about a year ago. Even if there is a problem in the product (and the support information usually indicates a problem in the product) it will not be fixed since the support for this product has ended. Upgrade to Acrobat XI, it is so much better for digital signing than 9.

HELP - Can no longer digitally sign documents on Adobe Acrobat Pro ver 9 ?

Was able to for the last 8 - 10 months then 2 weeks ago it stopped (intermittently). Now when I go to sign I get through the process and can see my signature on the docuemnt but then I get this error "creation of this signature could not be completed" unknown error - support information CSigDict-1938" and cannot save it.
I deleted my signature and re did it but that has not helped. I am running Windows 7
thanks

Support information has a value as long as the product is supported. I believe Adobe ended Acrobat 9 support about a year ago. Even if there is a problem in the product (and the support information usually indicates a problem in the product) it will not be fixed since the support for this product has ended. Upgrade to Acrobat XI, it is so much better for digital signing than 9.

Digitally signed documents causing Acrobat 9.3.1 to crash

Multiple users at my office are experiencing problems with digitally-signed PDFs. As soon as anyone tries to open the PDFs that have been signed, Acrobat crashes. We're using Acrobat 9.3.1 (32-bit) on 64-bit Windows 7. Reinstalling Acrobat has not helped. Adobe Reader 10 can open the documents successfully. I can duplicate the problem on any machine.

Reader 10 was not installed on the same machine, no. Upgrading to 9.5.1 is not currently an option, nor will it become one for several months. We are in a corporate environment that is currently standardized on 9.3.1, and we have a number of applications that are dependent on that specific version. What other options can you offer that allow us to stick with Acrobat 9.3.1?

Getting Error:Digitally Signing documents using Acrobat SDK

I am using following API's to digitally sign a document using Acrobat SDK but getting error(return code -2) while making a call to folllowing API DigSigCommitSigRefDict(ASAtomFromString("DocMDP"), tempDict, &pOutRefDict);
What am i missing?
Here's my code.
    CosObj sigDict = CosNewDict(cosDoc, true, 1L);                         //Signature Dictionary Cos Object
    CosObj sigRefDict= CosNewDict(cosDoc, true, 1L);                    //Signature Reference Dictionary Cos Object
    CosDictPut(sigRefDict, ASAtomFromString("TransformMethod"), CosNewName(cosDoc, false, ASAtomFromString("DocMDP")));
    CosDictPut(sigRefDict, ASAtomFromString("Type"), CosNewName(cosDoc, false, ASAtomFromString("SigRef")));
    refArrayObj = CosNewArray(cosDoc, false, 1L);                         //Reference array object inside signature dictionary
    CosArrayInsert(refArrayObj,1, sigRefDict);
    CosDictPut(sigDict, ASAtomFromString("Reference"), refArrayObj);
    CosDictPut(sigDict, ASAtomFromString("Type"), CosNewName(cosDoc, false, ASAtomFromString("Sig")));
    CosDictPut(sigField, ASAtomFromString("V"), sigDict);               //SigField is an AcroForm object
    DSSigRefDictParamsRec myDSSigRefDictParams;
    myDSSigRefDictParams.size = sizeof(DSSigRefDictParamsRec);
    myDSSigRefDictParams.cosDoc = PDDocGetCosDoc(pdDoc);
    myDSSigRefDictParams.rootObj   = cRoot;
    myDSSigRefDictParams.sigDict   = sigDict ;
    myDSSigRefDictParams.transformMethod   = ASAtomFromString("DocMDP");
    //myDSSigRefDictParams->transformParams   =
    myDSSigRefDictParams.bIndirect    = true;
    DSSigRefDictErrParams errParams;
    DSRetCode retCode = DigSigNewSigRefDict(&myDSSigRefDictParams,errParams);
    CosObj pOutRefDict;
    retCode = DigSigCommitSigRefDict(ASAtomFromString("DocMDP"),sigDict , &pOutRefDict);
    retCode = DigSigFinishSigRefDict(ASAtomFromString("DocMDP"), sigDict , pOutRefDict,errParams);
-amit

Thanks for the tip George. I'm using Acrobat Pro X to create a form. Can you tell me how to make the form reader-enabled so that it can be digitally signed?
Josh

Can't digitally sign document

Since we have upgraded to Reader version 9, anytime we send a PDF through email that requires a digital signature. The digital signature option is grayed out. When you check the properties of the document it says that digital signatures are not available. If we try the same document with Reader version 8 we are able to digitally sign the document. Are we doing something wrong when creating the documents? We use Adobe Acrobat 7 Professional for creating the documents. Any help would greatly be appreciated. I can send one of the documents if someone things they know what may be wrong.

Similar issues here, but the document properties say that it is allowed.
I am new to this and this is the first time I've set it up. It appears that I have everything done but it still won't let me sign.

Digitally signing documents using Adobe Reader

Can PDF forms created using Acrobat be digitally signed using Adobe Reader?

Thanks for the tip George. I'm using Acrobat Pro X to create a form. Can you tell me how to make the form reader-enabled so that it can be digitally signed?
Josh

Why are the colors in my digital booklet super saturated on my iPad?

I find it ridiculous that I have to change the format of the digital booklet in the first place, but after I did that I transferred it to my iPad, opened iBooks and my digital booklet's colors re so saturated I could read half of the words in the book because they were black. How do I solve this??? Is it a bad download?

Hi again John,
Now I am sitting in front of the right computer and I just checked the CMYK profile in AI and it says: North America Prepress 2. I found the following tutorial on the internet and this guy says that it is best to use a CMYK profile called BEST WORKFLOW which is supposed to accurately display colors across all platforms. In the tutorial, he also added that if you do not see this profile listed then you should Load (directly from the CMYK profile window) it from your computer. However, I was unable to locate this profile on my MAC and since this tutorial is based on AI CS2, I am unsure if I can use it.
http://www.bing.com/videos/watch/video/adobe-illustrator-cs2-how-to-use-color-settings/85f 81f66adab4d48746e85f81f66adab4d48746e-562401182564?q=adobe+illustrator+cmyk+color+profiles &FROM=LKVR5&GT1=LKVR5&FORM=LKVR
Which CMYK profile would you recommend that I use?
Many thanks,
Diane

Why does the newest FF keep me signed in to websites when I log off despite being set to full time "private browsing"? This is a real problem on a shared computer!

Despite being set to full time "Private" mode, this latest version of FF keeps me logged into things like ebay etc.
This has never happened with previous versions and is a real problem.

Are you restoring pages from the previous session if you start Firefox?
*https://support.mozilla.com/kb/Session+Restore
Start Firefox in [[Safe Mode]] to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
*Don't make any changes on the Safe mode start window.
*https://support.mozilla.com/kb/Safe+Mode
If clearing the cookies doesn't help then it is possible that the file cookies.sqlite that stores the cookies is corrupted.
Rename (or delete) cookies.sqlite (cookies.sqlite.old) and delete cookies.sqlite-journal and cookies.txt, if they exist, in the Firefox Profile Folder in case the file cookies.sqlite got corrupted.
* http://kb.mozillazine.org/Profile_folder_-_Firefox

Why is the validity of my digitally signed document displayed as unknown?

Similar Messages

Maybe you are looking for