Quantcast
Channel: Adobe Community: Message List - Extension does not contain valid signature
Viewing all 106 articles
Browse latest View live
↧

Extension does not contain valid signature

September 13, 2011, 5:36 am
$
0
0

Hi all,

 

I open again a thread about a problem at our extension installation on several computers.

Few persons can't install our extensions. They get this message: " The extension xxx does not contain valid signature. The extension will not be installed"

 

Our plugins worked always since the beginning ( about December 2010 )

Our certificate is valid and has been created by TrustCenter.

I use ucf.jar with correct parameters...

 

I thought that's a manifest problem. So, I tried to generate plugins from Extension Builder trial version which generates manifest "automatically" but the result is the same. I also tried to get a release from a non-signed certificate ( 1024-RSA and 2048-RSA )....but unsuccessfull...

 

How to get a extension with valid signature for all computers ?

 

Thanks.

Regards.

 

Pierre RAFFA
Aquafadas

↧
Search

Re: Extension does not contain valid signature

September 13, 2011, 6:28 am
$
0
0

Pierre

 

Has your certificate expired? This sounds like the same problem as reported on this thread: http://forums.adobe.com/message/3801447

 

If so, scroll down to post 5 (one of my replies) on that thread and you'll see an explanation for the behaviour. Sadly it is a bug in Extension Builder and ucf.jar documentation.

 

Assuming this is the problem you're having, I think your solution would be to obtain a valid certificate, and resign your extension using the Packaging and Signing Toolkit, specifying the tsa argument. I'm sorry for the trouble this has caused. We have a bug open against Extension Builder (#2923679), it will be fixed in the next release.

 

David.

↧
↧

Re: Extension does not contain valid signature

October 6, 2011, 2:16 pm
$
0
0

David, we are having the same problem: an extension signed with a valid certificate and with timestamp, using ucf.jar, valid manifest, installs without problems on some machines, but gives "The extension does not contain valid signature." error on some customers' machines (the reported one is Mac OS 10.7.1, with CS5.5).

I checked the "signatures.xml", it does contain a "TimeStamps" section.

You can download the extension here: http://bit.ly/nzChAJ

 

Can you please take a look? I suspect there is some problem with the signature checker in CS5.5 as Pierre reports similar problems.

 

 

Thank you,

Anatoly

↧

Re: Extension does not contain valid signature

October 7, 2011, 3:38 pm
$
0
0

Anatoly, I will try to reproduce this behaviour but it will take me some time to get set up. In the meantime can you help to isolate the issue by bypassing Extension Manager and installing the ZXP directly.

 

- Quit Photoshop if it is running

 

- Unzip the zxp's contents

 

- Copy the unzipped contents to /Library/Application Support/Adobe/CS5.5ServiceManager/extensions/com.pixelnovel.timeline

 

- Ensure the CSXS PlayerDebugMode flag is *not* set to 1 (the default should be 0 or non-existent) in /Users/<username>/Library/Preferences/com.adobe.CSXS.2.5.plist. This means that only signed extensions should get loaded.

 

- Launch Photoshop and load your extension.

 

Does the extension load correctly?

↧

Re: Extension does not contain valid signature

October 11, 2011, 5:30 pm
$
0
0

I have tried to reproduce the installation issue with your extension on OSX 10.6.8, 10.7 and 10.7.1 but in each case I can install the extension okay. When I run it, I get a missing/broken swf icon (see below), but I don't think that is symptomatic of a signature problem.

Screen shot 2011-10-11 at 17.29.29.png

I have asked the Extension Manager team if there are any known issues in this area which might explain the behaviour you are seeing.

 

If you can provide answers to the above or any other information which might help isolate the issue please do.

↧
↧

Re: Extension does not contain valid signature

October 12, 2011, 9:13 am
$
0
0

Update - the Extension Manager team believe they have reproduced this on 10.7.2 and are investigating. I will keep you posted.

↧

Re: Extension does not contain valid signature

October 12, 2011, 2:23 pm
$
0
0

Thank you David,

 

Sorry for the delay with response - I was swamped with other activities.

 

You are correct, the extension doesn't work even if it succeeds to install, however the problem is that on some Mac machines it fails to install.

 

I'm glad that the Extension Manager team have managed to reproduce it. All I can say that the problem does not happen on all Macs - I couldn't reproduce it on my Mac OS 10.7.1, but a customer with the same version of Mac OS said that they got the "incorrect signature" error.

 

Do you think that the fix will be in the extension, or the users will need to update Extension Manager?

 

Please keep me updated on this issue if it's possible.

 

Thank you,

Anatoly

↧

Re: Extension does not contain valid signature

October 19, 2011, 8:49 am
$
0
0

Hi David,

Did you hear anything from the Extension Manager team on this issue? We have another customer reporting this on Mac OS 10.7.2...

 

Thanks,

Anatoly

↧
Search

Re: Extension does not contain valid signature

October 19, 2011, 10:59 am
$
0
0

They have reproduced it and are trying to understand the cause. Sorry for the wait. I will let you know as soon as I hear from them.

↧
↧

Re: Extension does not contain valid signature

October 19, 2011, 2:46 pm
$
0
0

Hi David,

 

We're currently having the same problem. I'm adding what I know to this thread with hope that it will help you troubleshoot the problem.

 

An extension with a valid timestamped signature is rejected by the Adobe Extension Manager on installation (root CA is VeriSign; the certificate has not expired; extension packaged and signed with ucf.jar with a tsa URL). This is happening on computers running Mac OS X Lion 10.7.2 with CS5 and CS5.5. The same extensions that we have a problem installing now used to work on OS X Lion with both CS 5 and CS 5.5 a while ago, but since upgrading to the latest software from Adobe and Apple we get the an error message saying "The extension XXX does not contain valid signature. The extension will not be installed". However, the same extension that's rejected on the Mac can be installed and works without any issue on computer running Windows 7.

 

Thanks,

Daniel

↧

Re: Extension does not contain valid signature

October 20, 2011, 2:27 pm
$
0
0

David, do you know if there is a temporary workaround for this problem? Would unchecking the "Show warnings when installing unsigned ZXP extension" in the Extension Manager settings help?

 

Thanks,

Anatoly

↧

Re: Extension does not contain valid signature

October 20, 2011, 8:09 pm
↧

Re: Extension does not contain valid signature

October 21, 2011, 2:23 pm
$
0
0

Hello Carl,

Thank you for your response.

 

I've signed our extension with the new ucf tool and sent it to a customer for testing - I will let you know once we get some feedback.

I cannot attach files to posts here (looks like it's a privelege of Adobe's employees), but the file I used was download from here: http://download.macromedia.com/pub/developer/creativesuite/extension-b uilder/signingtoolkit.zip

 

I am not quite sure what exactly I need to pay attention to regarding canonicalization limitations - I have no idea how the ucf tool works, and even if I did, I have no control over the verification process, so I am not sure why you are referring me to that document. Can you please elaborate?

 

Thank you,

Anatoly,

PixelNovel

↧
↧

Re: Extension does not contain valid signature

October 23, 2011, 7:30 pm
$
0
0

I don't know how ucf.jar works either. Sorry for the confusion caused by me. It should be taken care by ucf.jar or any signing tools. Could you please send the new signed extension to me so that I can test it? I can reproduce this problem with the old extension you gave in previous post. You can get my mail address from the private message.

↧

Re: Extension does not contain valid signature

October 24, 2011, 2:59 pm
$
0
0

Hi,

 

We are facing the same issues and urgently need to provide an update to our customers but its hard when we know they won't be able to install the update.

We tried to revert to the previous MAC version but this didn't help. Their also doesn't seem to be a difference between CS5 and CS5.5.

Can you confirm this? As the cause been located? Is their a workarround available?

 

Any help is aprreciated! Thanks!

↧
Search

Re: Extension does not contain valid signature

October 24, 2011, 6:57 pm
$
0
0

this issue should also exist in CS5 although I didn't check it with CS5. If your extension is a CSXS extension (no *.mxi file in package), you can use the workaround provided by David in third reply to install the extension manually. Note that you have to change the folder name "com.pixelnovel.timeline" in that post to the ExtensionBundleId of your extension (in manifest.mxl).

↧

Re: Extension does not contain valid signature

October 24, 2011, 7:39 pm
$
0
0

Deleted my last post as it was based on some misunderstanding on my part. Please try as Carl suggests above and report back

↧
↧

Re: Extension does not contain valid signature

October 25, 2011, 9:54 am
$
0
0

We have a bunch of different machines, and this bug is definitely 10.7.2 specific.

↧

Re: Extension does not contain valid signature

October 25, 2011, 11:16 am
$
0
0

Hello!

 

All my customers on Lion started experiencing the same problem! The new ucf.jar does NOT help. I tried it myself installing with Extension Manager CS5.5 and Lion 10.7.2 - I got the same error!

Please fix it, as noone can now install extensions on Mac OS X Lion.

 

P.S. Extensions now do not run at all on Lion 10.7.2, even if I copy it to CS5.5ServiceManager/.... folder. I got the blank panels.

 

Thank you

↧

Re: Extension does not contain valid signature

October 25, 2011, 11:23 am
$
0
0

Maybe it's time to get rid of the whole silly signing business?

 

We've been able to install plugins and scripts for forever without signing them and noone worried until now.

 

Why did we need to make this complicated with CS Extensions?

 

Harbs

↧
Viewing all 106 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>