Rapidboot Version 1.2 corrupt digital signature

The previous verion of Rapidboot ran with no errors. I downloaded the latest version 1.20 and it installs fine but fails to run with the following error in the system event log.
The PHCORE service failed to start due to the following error:
Windows cannot verify the digital signature for this file. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might versiobe malicious software from an unknown source.
I have downloaded v1.2 multiple times using different browsers and still get the same failure when I install it. Uninstall/reinstalls also do not resolve the problem. I have reinstalled the previous version with no problems or errors encountered.
Could Lenovo really have release Rapidboot with a bad digital signature? Note that this is the 64bit windows 7 version and that the file I believe is in question is phcore64.sys
Any suggestions/solutions would be appreciated.
Thanks

Hello,
You might want to check this message thread; it seems to discuss a similar problem.
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество

Similar Messages

Xfa Form, Digital Signatures, file attachments and Reader 9

Hi,
In reader 8 and previous, when i wanted to have a form that could be signed, passed to the next persons, added attachement signed, repeat, while maintaining the signatures valid, i could.
Since we updated to reader 9.12 all previously signed documents appear with invalid signatures and if i try to attach a file, the add button just isn't there.
If i follow he following steps:
Server side:
- Create PDF from xdp + xml (using forms).
- Assign Form Fillin, Digital Signatures and File Attachment (using Reader Extentions)
Client side:
- Populate the Form data
- Attach files
- Certifiy
- Sign (multiple Signatures)
It works fine, but it isn't the workflow i had in previous versions.
The workflow i have here is:
Server side:
- Create PDF from xdp + xml (using forms).
- Assign Form Fillin, Digital Signatures and File Attachment (using Reader Extentions)
Client side:
- Populate the Form data
- Attach files
- add Signature (only locks a collections of form fields)
- Repeat until everyone has attached their files and signed.
The problem is that this worked fine in versions before 9 (all digital signatures here validated with the yellow exclamation mark indicating new content), but in 9 and up what i get, after validating the signatures in reader, is a information indicating that the signatures are invalid because the document is either corrupt or has been changed.
Is this a bug or has this been changed from version 8 to version 9?
I've read the changelist of reader 9 and it talks nothing about this situation or Digital Rights other than form fillin, annotations and digital signtatures (the ones we can choose in the certification wizard of Acrobat Pro).
Any idea if its possible to implement the second scenario in reader 9, or even if its possible? Is there a guide on the practices Adobe garaties will allow to validate signatures in the following years? Even if it means usings PDFA.
Thanks in advance.

One last try.
You help would really be welcome in finding out the root cause of the difference in behaviour between reader 8 and 9 in this matter (bug or change).
I have no idea what documentation to read (since i've read the launch documentation and change list documentation) about reader 9, i've contacted Adobe 3 days ago (and the answer is silence, like usuall) and have no clear thought about what to say (without taking a huge risk by giving a uninformed answer) about this issue.
Thanks.

Digital signatures with different versions of Reader

I have created a form which requires a digital signature for approval. Typically, an employee will complete the form in Reader and forward it to a supervisor for approval. The supervisor needs to sign it digitally and forward it to me.
The issue we are having is with those employees who are completing the form in Reader and the supervisor (or someone thereafter) has a more updated version of Reader and cannot sign the document. What can we do to stop this from happening? There is no practical way to keep everyone on the same version of Reader. We will have many more forms which require a signature, and we need this issue resolved. (I am using Adobe Acrobat 9 Pro to create the forms.)
Also, is there a way to verify the digital signature without using a third-party source? At this point, we know anyone can create a digital signature using someone's hand-written signature they found on another paper and we would like to prevent this from happening. We need to validate the person who used the digital signature is really that person.
Any help is appreciated! Thank you!

If you are creating your forms in Acrobat 9 Pro. and then Reader-enabling them for digital signatures, then recipients of the form will need to use at least version 8 of the Adobe Reader. Also, you'll need to do a few things during the authoring stage of your form, if your form changes by role (i.e., additional data is entered, annotations, or multiple signatures). Mainly you'll need to use a certification sig. for the first signature and set permitted changes after certifying.
You can find a lot more detail on best practices on developing forms for multiple signatures in the Digital Signature User Guide at:
http://www.adobe.com/devnet/acrobat/pdfs/acrobat_digsig_userguide_90.pdf
The guide also explains how to validate documents (authenticity validation and document integrity validation).

Since upgrading to version 11, I am unable to paste a signature image -- being forced to use a digital signature.

I would like to be able to place a signature image, as I did in previous versions. It seems as if I am being forced to use a digital signature, which the other side is not prepared to accept.

Hey there Jantje1,
It sounds like you are unable to launch iTunes and get an error message instead. I would try the troubleshooting outlined in this article named:
iTunes for Windows Vista, Windows 7, or Windows 8: Fix unexpected quits or launch issues
http://support.apple.com/kb/ts1717
If it comes down to uninstalling, then re installing iTunes altogether, use this link to download the 64 bit version of iTunes directly.
iTunes 11.1.3 for Windows (64-bit)
http://support.apple.com/kb/DL1615
Thank you for using Apple Support Communities.
Take care,
Sterling

Form 16 With digital signature giving adobe document corrupted output

Dear All,
We have configured ads and implementing form 16 with digital signature,we have done the all configuration as per SAP Guide and dezso blogs,but when generating the form 16 with digital signature its giving
"Adobe reader could not open _xxxxx.pdf because it is either not a supported file type or corrupted,
we have done the same configuration in dev its working fine and prd its not working,request you to please provide the solution for the same.
as per some check list i have cheked ads_https is working fine,but when executing the report fp_pdf_test_00 with rfc ads_https its asking for user name and password,we have maintained the same user name and password for abap and java for both adsuser and ads_agent still same issue,
pelase suggest.
please find attached screenshot for your reference.
Regards,
Basis

This can be done but you must use the Document Form var to route the signed pdf. You must configure the FormGuide submit button to 'Submit from PDF' in Guide Builder.
Also the button on the form must be configured to submit as 'PDF' (not XDP). This change is done when you open the form in designer.
Note that after you have submitted the signed pdf you will be dealing with a pdf subsequently.
Attached is a sample FormGuide.

I have acrobat 8 and my digital signature has been corrupted. How do I fix that?

I have acrobat 8 and my digital signature has been corrupted. How do I fix that?

Make a new one.

Invalid Digital Signature and corrupted files???

ever since i have been asked to upgrade to 7.2, i have not been able to ugrade to 7.2 due to a invalid digital signature. and when i tried to DL music it always says corrupted file try again later, been like that for a week, and i have a spy-sweeper which i've disengaged to see if it helped, nope.

ever since i have been asked to upgrade to 7.2, i have not been able to ugrade to 7.2 due to a invalid digital signature.
although the following document refers to a slightly different error message, perhaps give it a try:
iTunes: Windows reports that iTunesSetup.exe is not a "valid Win32 application"
... but if no joy there, try the following Microsoft document:
(MS) You cannot install some updates or programs

How to add digital signature to Form16 in version 4.7?

I need to add a digital signature to the Form 16.
i read somewhere that this can be done thru smartforms.
can someone please tell me how it can be done?

Cannot be done on 4.7

Digital signature on mobile version on MS Office

Hi,
I need to put digital signature (using certificate) for MS office documents using mobile device. In Microsoft Office Mobile app it is not possible to do this. Please guide me how can I achieve this.
Is there any mobile API suitable for this case?

Hi jplotnicki,
As far as I know, there'no API for Office Mobile yet.
You can submit a feedback in Office Developer Platform here:
Customer Feedback for the Office Developer Platform
Thanks for your understanding.
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Forms, digital signatures, cross platform issues

I am trying to implement pdf forms in an educational environment to utilize digital signatures and reduce paper. The form data does not need to go anywhere. It just stays in the form at this point. Some people on campus have Windows machines, others have Macs. All the Windows machines have Acrobat Pro installed and not Reader. The Mac people are more likely to have Reader. There have been problems with emailing these forms between platforms. Does anyone have any ideas about how to solve this? My IT department will not support Reader on Windows machines, so the forms have to work in Acrobat and Reader! How should the orginal document I put online be saved to work in both programs and platforms? What direction should I give the users about how to save the forms they fill out and sign? I've looked all over for this kind of info, but can't seem to find it. Any and all help is greatly appreciated. FYI, I am not an IT person. Thanks!!!

For Mac users, it will be important that they don't use the Preview application to work with the forms. Preview is the default Mac PDF viewer out of the box, and it corrupts PDF forms when it saves them, so it really needs to be avoided.
In order for Reader to save a filled-in form and apply digital signatures, the forms need to be Reader-enabled, which can be done with Acrobat Pro. Acrobat Standard can Reader-enable documents too, but it doesn't apply the digital signature usage right.
The problem with this is if you will be getting the forms returned to you, you can only use data from no more than 500 instances for the form, including hardcopies. This is an Acrobat License Agreement restriction. If they won't be returned, there won't be a problem. Also, the Acrobat users don't need to use a Reader-enabled version, so you can collect all the forms you want from them.
Email will be most reliable if the user manually attaches the file to an email, as opposed to setting up a button on the forms to submit to an email address. You'll find many threads here discussing the emailing difficulties with forms that are set up this way. The problems can be minimized with user education, as the manual process is available in either case. A submit button provides convenience, unless it doesn't work, and it won't for some users.

Digital signature in Software Update

I have been trying to Update my Tiger version 10.4 to 10.4.3 using Software Update. After the files download, I get a comment that says the digital signatures are not correct the files cannot be installed. What does this mean?

"The digital signature for this package is incorrect. The package may have been tampered with or corrupted since being signed by Apple"
My iMac Flat Panel updated the most recent upgrade just fine, but my iMac Classic showed the above error message.
I tried several times over two days but no go ... finally I downloaded the OS X 10.4.4 file on Apple's Support site http://www.apple.com/support/downloads/macosxupdate1044.html ... it installed just fine. Then I went to Software Update and this time QuickTime, iPhoto and iPod updates installed without error.

The error occurs by correspondence check (WinVerify Trust) of the signature when Windows Installer with the digital signature is executed.

The following errors occur by correspondence check (WinVerify Trust) of the signature when Windows Installer with the digital signature is executed.
"Error 1330. A file that is required cannot be installed because the cabinet file C:\<tool>\Data1.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt. Error 8230 was returned by WinVerifyTrust."
Please teach the following of Error 8230.
1) Occurrence condition.
2)Approach to avoiding.

So I found my own answer to the issue. The error was being caused by an the following xml in the assertion:
<ds:Reference URI="">
The value of URI attribute must have a '#' followed by the same value of the ID attribute in the parent 'Assertion' element (in our case a random string):
<saml:Assertion xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion" ID="a5k42vnhsywezqzyufq15c4bb9xuzeozrmbppj38xe" IssueInstant="2012-03-12T14:33:25.986Z" Version="2.0">
<saml:Issuer>ISSUER_NAME</saml:Issuer>
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/>
<ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/>
*<ds:Reference URI="#a5k42vnhsywezqzyufq15c4bb9xuzeozrmbppj38xe">*
How this is related to the digital signature is beyond me, though I admit I'm very new to saml and digital signing. However I spent a great deal of time investigating my certs and how I was creating the signature, which it seems is unrelated to the actual issue. I also wasn't able to find any docs specifying that this attribute was required, though I might have just missed it.

Error encountered while BER decoding Digital Signatures

Hello -
I work for a GOV agency and we use Common Access Cards/Smart Cards to login to our PC's and we subsequently use them to digitally sign PDF documents.
We have just recently switched to Adobe Acrobat 9.x Pro. Before this, we had Adobe 7.x Pro and had no troubles digitally signing documents, clearing those digital signature to reuse old documents, etc.
We first got Acrobat 9.x and had issues with digital signatures right away. We had to import this into the registry, which I believe I found on adobe forum.
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Security\cASPKI\cASPKI\cCustomCertPrefs\c4974BB0C5EBA7AFE0254EF7BA0C695C60980 7096]
[HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Security\cASPKI\cASPKI\cCustomCertPrefs\c4974BB0C5EBA7AFE0254EF7BA0C695C60980 7096\cAdobe_OCSPRevChecker]
[HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Security\cASPKI\cASPKI\cCustomCertPrefs\c4974BB0C5EBA7AFE0254EF7BA0C695C60980 7096\cAdobe_OCSPRevChecker\cURL]
[HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Security\cASPKI\cASPKI\cCustomCertPrefs\c4974BB0C5EBA7AFE0254EF7BA0C695C60980 7096\cAdobe_OCSPRevChecker\cURL\c0]
"sValue"=hex:68,74,74,70,3a,2f,2f,6f,63,73,70,2e,64,69,73,61,2e,6d,69,6c,00
[HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Security\cASPKI\cASPKI\cCustomCertPrefs\c4974BB0C5EBA7AFE0254EF7BA0C695C60980 7096\cAdobe_OCSPRevChecker\cURLToConsult]
[HKEY_CURRENT_USER\Software\Adobe\Adobe Acrobat\9.0\Security\cASPKI\cASPKI\cCustomCertPrefs\c4974BB0C5EBA7AFE0254EF7BA0C695C60980 7096\cAdobe_OCSPRevChecker\cURLToConsult\c0]
"iValue"=dword:00000001
Lately we've had trouble verifying signatures. Once we sign a document and then click the signature, we get the attached error.
Error during signature verification
Error encountered while validating
Error encountered while BER decoding
When we started to notice this we were on Acrobat 9.2. I think we may have went from 9.0 to 9.1.3 and then to 9.2 pretty quick. I removed it and installed our base load of Acrobat 9.0 and everything was working fine. I then updated to 9.1, 9.1.1, 9.1.2, 9.1.3 and none of them worked or fixed the issue. We have recently approved the update to 9.3, but that didn't fix it either. Because of this BER decoding issue, we cannot right click the signature field and clear a signature as well. Even after updates I could clear a signature field signed under Adobe 9.0.
Adobe, what should I do? Do we have a problem elsewhere, outside of Acrobat?
Again, we use smart card's to sign the documents, thus cannot change certificates.
Thanks, Nick

Hi Nick,
When you mentioned that upgrading to 9.3 didn't fix the problem, did you mean when creating a new signature in Acrobat/Reader 9.3 or did you mean opening a previously signed file and doing the signature verification?
If you meant the later, no version of Acrobat will be able to decode the signature if it was created incorrectly, which is what I fear you are referring to. What happened was Acrobat 9.0 changed the default digest method from the older SHA-1 to the the new SHA-256, but if the device that encrypts the digest (the actual signing operation) cannot handle the larger digest Acrobat is supposed to fall back to the older, smaller SHA-1 digest. There was a bug where Acrobat wasn't re-computing the digest if the smart card couldn't handle SHA-256 and creating a corrupt signature. Once this corrupt signature is written out to the PDF file there is no getting around it. Update 9.3 fixes the problem at signature creation and you should be able to successfully sign using your CAC card, but sadly there is no fixing the existing corrupt signatures.
Steve

Acrobat Standard 8 - why is the digital signature not responding?

Using Acrobat version 8 and it is fully updated.
When I try to insert a digital signature, it freezes and when I eventually close the digital signature window, it says it is not responding and the program shuts down.
This is using a document that I use frequently and only recently started having problems with the digital signature.
Why is this happening and how can I fix it?
Thank you!

Hi,
I'd like to clarify some points. You use a digital ID to create a digital signature, not unlike how you use a pen to create (what we refer to as) a wet ink signature. When it comes to applying a digital signature to a document, you can sign just about any blob of electronic data. You can sign your e-mail or a MS Word document as well as a PDF file. The signature itself lives either in the document (that's how Acrobat does it when signing a PDF file), or it can be an external attachment (that's what the smime.p7s file is you might see attached to some e-mail messages).
Here is where I'm a bit confused. How many digital IDs do you have access to? If you only have one, does it cause Acrobat to lock up when signing a specific PDF file or when you try to sign any PDF file? Same question if you have more than one digital ID available to sign with, they all cause Acrobat to lock you when signing just one specifc file or any file? When you try to sign, are you signing an existing signature field, or are you creating a signature on the fly, be it either visible or invisible? If it is just one file that is causing the problems then that file is probably corrupt. If it's any file then it is a more systemic problem and I don't have an off the shelf answer for you.
Steve

Digital Signature Incorrect?

In the process of updating my iTunes software (using Software Update from Preferences) to the latest version 8.2.1 I received this message ...
The update “itunes” can’t be installed.
The digital signature for this package is incorrect. The package may have been tampered with or corrupted since being signed by “Apple.”
I note I've had recent similar problems when attempting earlier upgrades including the latest “Security Update 2009-003 (PowerPC)” upgrade.
After looking through this forum it was suggested that one should download the latest version of iTunes directly from the Apple download website at http://www.apple.com/itunes/download/ and try the install again.
I did that and completed the download of the iTunes8.2.1.dmg file to my desktop but, when I clicked on it to install I received the following message ...
The Following disk images failed to mount
iTunes8.2.1.dmg – Reason: invalid checksum
What's up with that? Suddenly I'm unable to update any of my software without receiving at least one of the above two messages?
Any ideas how to fix the problem?
Thanking you in advance.
Rick

I am having this trouble with several updates I've been trying to do with an eMac onto which I just installed 10.4 from scratch. The 10.4.11 combo updater wouldn't download or install because the verification check failed. I figured out a way around THAT, but now iTunes won't install, and java updates fail via Software Update for the same reason. I've been doing this for a lot of years and I've never seen this happen before!

Rapidboot Version 1.2 corrupt digital signature

Similar Messages

Maybe you are looking for