Improperly Signed Update.

Asked by jgarnham

I created my keys, added the public one to my project, generated the DSA signature, pasted it into Feeder, and it says its not been signed properly, i checked the DSA signature and it's exactly the same. Whats going on?

Question information

Language:
English Edit question
Status:
Solved
For:
Sparkle Edit question
Assignee:
No assignee Edit question
Solved by:
Hofman
Solved:
Last query:
Last reply:
Revision history for this message
Andy Matuschak (andymatuschak) said :
#1

Please post the commands you used to generate the signature and a link to your appcast.

Revision history for this message
jgarnham (joshua-garnham) said :
#2

App Cast Link : http://macrystal.com/spark-updates.xml
Commands To Generate Signature (After Navigating To Sparkle Distribution Directory):
ruby "Extras/Signing Tools/generate_keys.rb"

Revision history for this message
Hofman (cmhofman) said :
#3

That's the script to generate the keys. So how did you generate the signature?

Revision history for this message
Best Hofman (cmhofman) said :
#4

The 'signatures' in your appcast are far too long, I think they're in fact private or public dsa keys rather than signatures. That's consistent with your misundertsanding of the scripts. Please first read all of the documentation on setting up the appcast.

Revision history for this message
jgarnham (joshua-garnham) said :
#5

What's the difference between the signature and the key?

Revision history for this message
jgarnham (joshua-garnham) said :
#6

I just generated a signature and used the signature with the Update, and it still says it's improperely signed.

Revision history for this message
Hofman (cmhofman) said :
#7

> What's the difference between the signature and the key?

The difference is huge. The keys are generated once, and form a kind of password (there's a private key and a public key). The signature is generated from the private key and the update (.zip file), and can be checked using the public key. Again, please read the documentation, and check Google first.

> I just generated a signature and used the signature with the Update, and it still says it's improperely signed.

Are you sure you generated the signature correctly? E.g. did you use the correct keys (you should use the private key that was generated together with the public key embedded in your bundle)? Perhaps you can describe exactly what you did.

Apart from that you're not using a well formed version. The CFBundleVersion/sparkle:version should consist of digits and periods only (this is a system requirement). Moreover, your version numbers are not unique. So actually which version it will get is pretty much random. And at least 3 updates don't have a correct signature.

Revision history for this message
jgarnham (joshua-garnham) said :
#8

I just generated a signature that's made up of Letters and Numbers is this OK?

Revision history for this message
jgarnham (joshua-garnham) said :
#9

I've got rid of the old updates and yet it still doesn't work. This is the code I used:
ruby "Extras/Signing Tools/sign_update.rb" \
~/Desktop/Spark.zip ~/Desktop/dsa_priv.pem

Revision history for this message
Hofman (cmhofman) said :
#10

So did you use the correct private and public key? So are the files dsa_priv.pem you used to generate the signature and dsa_pub.pem you included in the bundle generated at the same time?

Revision history for this message
jgarnham (joshua-garnham) said :
#11

What do you mean at the same time?

Revision history for this message
Hofman (cmhofman) said :
#12

> What do you mean at the same time?

Generated as a single pair by the same run of the generate_keys.rb command.

Revision history for this message
jgarnham (joshua-garnham) said :
#13

Yes i did generate them at the same time.

Revision history for this message
jgarnham (joshua-garnham) said :
#14

Can you tell me why I am getting this problem?

Revision history for this message
Hofman (cmhofman) said :
#15

No, I can't tell you. I really think you're doing something wrong, but I can't say what, I don't have enough information and no clue left. I know the scripts work.

Revision history for this message
jgarnham (joshua-garnham) said :
#16

Ok, It works now, i don't know why, it just suddenly happened, I tried the code again then pasted it into the update and it worked.

Revision history for this message
jgarnham (joshua-garnham) said :
#17

Thanks Hofman, that solved my question.