Extension Versioning, Update and Compatibility - MDC - The Diigo Meta page

• 23 Jul 08
  

  Monabili Basumatary
  • How Applications Determine Compatibility
  • RDF format.
  • In either of the examples below, the sequence of the versions within the <RDF:Seq> element is significant, with the later versions needing to be presented after earlier versions. One does not need to list all versions if the latest version is being provided (?).
  • updateInfoURL entry to the update manifest (see the example above).
  • If you wish to serve your update RDF over regular http, Gecko 1.9 based applications will require that you digitally sign the update manifest to ensure that it's information isn't tampered with between you creating it and applications retrieving it. The McCoy tool should be used to sign the update RDF.
  • When the author creates the update rdf file a tool is used to sign it using the private part of the key. Roughly speaking the update information is converted to a string, then hashed using a sha512 hashing algorithm and this hash is signed using the private key. The resultant data is DER encoded then base 64 encoded for inclusion in the update.rdf as an signature entry.

  4 more annotations...

• 21 May 08
  

  Karsten Schmidt

  firefox extension plugin versioning rdf reference delicious

• 09 Feb 08
  

  Ed H Chi

  Firefox extension update

• 27 Jul 07
  

  Chad Burrus

  firefox extensions development

• 15 Nov 06
  

  Boris Goldowsky

  extension firefox reference

• 25 Oct 06
  

  Marco Frattola

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.