Problem with signing an update

Asked by Peter Appel

Hi all,

when initiating the update process first all looks fine. The download begins, but afterwards a second alert pops up, indicating an "The update is improperly signed"-error. I tried since hours, following strictly the instructions in the documentation, but still have no idea what is wrong.

Only one detail: when I sign the update with the Ruby script I always get a 2 line signature with a line break in between. I tried this a number of times, also with new created public and private keys but it always looks similar. I entered this signature in different ways in the appcast.xml but it never worked. (2nd line only, both lines without line break and with line break). For instance:

ruby "Extras/Signing Tools/sign_update.rb" ~/Desktop/MyApp.zip ~/Desktop/dsa_priv.pem
MEUCIAonkjhUhVaZdGEIcb99qVTL9PboM/yrLUAh/ugC6QIcAiEAiTLU/oyijrAQ
ak41RwMfxMyB1dCaJb5exJ6N5smwXwQ=

My appcast.xml looks like that:

<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:sparkle="http://www.andymatuschak.org/xml-namespaces/sparkle" xmlns:dc="http://purl.org/dc/elements/1.1/">
   <channel>
      <title>Trinity Changlog</title>
      <link>http://rhodesit.min.uni-kiel.de/~pa/appcast_tri.xml</link>
      <description>Most recent changes with links to updates.</description>
      <language>en</language>
         <item>
            <title>Trinity Version 1.7</title>
 <sparkle:releaseNotesLink> http://rhodesit.min.uni-kiel.de/~pa/trinity.html</sparkle:releaseNotesLink>
            <pubDate>Thu, 21 Oct 2010 20:20:11 +0000</pubDate>
            <enclosure url="http://rhodesit.min.uni-kiel.de/~pa/pub/software/Trinity.zip"
            sparkle:version="1.7"
            length="616466"
            type="application/octet-stream"
            sparkle:dsaSignature="ak41RwMfxMyB1dCaJb5exJ6N5smwXwQ="
             />

         </item>
   </channel>
</rss>

I'm using SL 10.6.4, with the latest Sparkle 1.5 b6.

Any help is greatly appreciated!
Thanks,
Peter

Question information

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

I wonder if you by chance have a newer version of OpenSSL installed than the one which ships with Snow Leopard?

People have been having a lot of signing issues due to this issue: http://github.com/andymatuschak/Sparkle/pull/15#issuecomment-468834

Try an "openssl version" at the command line for me?

If you've got the newer version, try getting the latest version generate_keys.rb from GitHub and using that.

Revision history for this message
Peter Appel (peap) said :
#2

Thanks Andy,

this solved my problem!

The ruby script used OpenSSL 1.0.0a 1 Jun 2010 at /opt/local/bin. I changed the scripts to use the default /usr/bin/openssl, which is OpenSSL 0.9.8l 5 Nov 2009 and all works fine now. I suggest to add a hint in the documentation for possible problems with the most recent version of openssl.

Thanks again!
Cheers,
Peter