Pinned Firefox 36 - Antigame origin no longer working

    • I don't know if TMoD02 is the same person I met at IRC, but the fix is simple. You just have to know the right position for single new code line.
      An update will be the latest released on Monday. This is due to my technical decision and my time (I have some events at the weekend!).

      the details
      In a firefox plugin you deliver an install.rdf-file and on the server an update.rdf-file. The update.rdf-file is authenticated via an antisymmetric signature. The public part is inserted in install.rdf-file, and the update.rdf-file keeps the signature. The corresponding private key to the public key in the installed extension is only on Francolino's computer. The other option seems to serve antigame.de with SSL. StartSSL has maintance on the weekend, so we need some time to prepare for future updates.
      OGame Tech

    • ImperatorMaximus wrote:

      I don't know if TMoD02 is the same person I met at IRC, but the fix is simple. You just have to know the right position for single new code line.
      Yes, I'm Skyscraper (InGame also known as TMoD02, or in RL: Malte). 8)

      It sounds easy, but if you're not an AddOn Developer it's not that easy. (I'm not, so it wasn't easy for me, too)
      So i recommend you to wait for the official new version. ;)

      Regards
      Malte

    • So. The new version is online! Because I am now tired, I only post the quote of my post in the german board and the a link to google translator.

      German

      ImperatorMaximus wrote:

      So nun mache ich mit den Forenposts Feierabend für heute.

      Ja, ich hatte eben die Versionsnummer der Website (und internen Update-Systems) unbedacht auf die neue Version 5.9.13.1 gesetzt. Da war aber die Datei noch nicht hochgeladen und hatte noch einen Fehler gefunden, welcher mir bei entflechten des Codes anscheinend passiert ist.
      Also noch mal nachbessern: Die Version für Firefox ist nun 5.9.13.2 und ist hochgeladen!
      Die Versionsnummer auf der Webseite und intern kann nun ich nicht anpassen, da mir währenddessen noch ein viel, dass die Chrome-Nutzer ebenfalls dann AGO intern ein Update angezeigt bekommen, ich aber natürlich kein Update für Chrome veröffentlicht habe oder gar im Chrome-Webstore veröffentlichen kann.
      Nun muss ich noch die interne Abfrage auf dem Server so manipulieren, dass FF-Nutzer ein Update angzeigt bekommen, Chrome-Nutzer aber nicht.

      Ganz abgesehen davon gibt es noch Probleme bei eingebauten Mechanismus des Firefox. Falls eine Erweiterung nicht unter »addons.mozilla.org« veröffentlicht wird (dann geschieht vieles automatisch), funktioniert der Update Mechansimus über 2 Dateien und dabei hat man auch noch 2 Wahlmöglichkeiten (so wie ich es jetzt verstanden habe. Falls das falsch ist, bitte ich um Aufklärung.).
      Es gibt in Add-Ons selbst eine Datei install.rdf. Dort ist die URL einer update.rdf angeben. Nun gibt es 2 Möglichkeiten, wie die Authentizität überprüft wird.
      Es können die Gegenstücke über eine digitale Signatur, welche mit einem Binary erstellt wird, welches bei mir unter ArchLinux nicht startet, überprüft werden, oder wenn die update.rdf (und co?) auf einem SSL gesicherten Server liegt. »Antigame.de« hat so nun ein kostenloses SSL-Zertifikat von StartSSL. Firefox möchtet zumindest über diese SSL geschützte Verbindung nicht die Erweiterung selbst installieren ("Certificate issuer is not built-in."). Davon, dass das SSL richtig konfiguriert und das Zertifikat richtig installiert ist, kann man sich unabhängig z.B. unter ssllabs.com überprüfen.
      Das bedeutet nun:
      antigame.de ist unter SSL verfügbar, bei mir unter Linux gibt es aber zumindest den Fall, dass Firefox die Installation der Erweiterung über SSL verweigert (kurzer Test mit Win7 / FF36 zeigten jedoch keine Probleme). Daher ist die automatische Umleitung auf die SSL-Version mittlerweile wieder deaktiviert und optional. Nach kreativen Ideen wird gesucht ;)

      Und nun mal dick für alle, die zu faul waren alles zu lesen, aber überfliegen:
      gefixte Version FF 5.9.13.2 mit SSL und ohne SSL

      English

      Google Translator wrote:

      So now I'm doing with Forums Posts closing time for today.

      Yes, I just had thoughtlessly put on the new version 5.9.13.1 version number of the site (and internal update system). However, since the file was not uploaded and had found a bug, which apparently happened to me at disentangling the code.
      So make further amendments: The version of Firefox is now 5.9.13.2 and is uploaded!
      Publish the version number on the website and internally now I can not adjust because while me a lot that Chrome users get also then AGO internally displayed an update, but I of course no update for Chrome have published or even in the Chrome Webstore can.
      Now I have to manipulate so that FF users get an update YaST Online Chrome users but not the internal query on the server.

      Quite apart from this, there are still problems with built-in mechanism of Firefox. If an extension is not published under "addons.mozilla.org" (then much done automatically), the update works Mechansimus about 2 files while you also have 2 choices (as I have understood it now. If that is wrong, I ask for an explanation.).
      There are add-ons install.rdf file itself. There, the URL is a update.rdf specify. Now there are two ways in which authenticity is checked.
      It can counterparts on a digital signature is created by a binary that does not start with me under ArchLinux be checked, or if the update.rdf (and co?) Perched on a SSL secured server. »Antigame.de" so now has a free SSL certificate from StartSSL. Firefox does not want to at least this SSL secure connection even install the expansion ("Certificate issuer is not built-in."). Assume that the SSL configured correctly and the certificate is installed correctly, you can independently eg Check under ssllabs.com.
      This means now:
      antigame.de is available under SSL, with me on Linux but there is at least the case that Firefox refuses to install the extension via SSL (short test with Win7 / FF36 but showed no problems). Therefore, the automatic redirection to the SSL version is now deactivated and optional. After creative ideas is wanted;)

      And now even thick for those who were too lazy to read anything but skim:
      fixed version 5.9.13.2 FF with SSL and non-SSL
      OGame Tech

    • Good to hear that progress has been made on the situation and there is the update available, what concerns me though is there is no changelog for it on the antigame website. Is this because it can't be accessed or because it is just the line of code that has been changed to work with firefox 36?

    • Ok, i installed firefox 35 and antigame works, but the programm autoupdated, and i have 36.0 again, and AGO still not working, i readed that problem solved, and i tried to reinstall AGO, but still not working :huh:

      Could someone tell me how to desactivate autoupdate, or how i can solve the problem?

      Sorry for my english, im learning :D


    • pescaderoloco      :

      My English is terrible too, don't worry :)

      Try these steps:

      0. uninstall firefox

      1. download firefox installer 35 (portable recommended)

      2. turn off the Internet.

      3. install firefox 35 (portable recommended)

      4. turn off autoupdate in firefox settings

      5. close firefox

      6. turn on the Internet.

      7. start firefox

      8. install AGO

      9. Enjoy!

    • I can confirm AGO 3.9.13.3 works with FF36 on both windows and linux. Are you sure you updated your AGO to this version (check addons page)? Trying to update it from addons page didn't work for me (though this was with version 3.9.13.2 so I don't know if that's changed now with new version), however reinstalling it from antigame.de worked fine.

    • hynner wrote:

      I can confirm AGO 3.9.13.3 works with FF36 on both windows and linux. Are you sure you updated your AGO to this version (check addons page)? Trying to update it from addons page didn't work for me (though this was with version 3.9.13.2 so I don't know if that's changed now with new version), however reinstalling it from antigame.de worked fine.

      Yeah, im sure, i use Windows 8, and it didnt work, i install AGO from the official site (i guess its the official, i go on by google) and i see this page, i delete late version, i click on install but with Firefox 36 dont work

      Image: