Users of the unstable version: please note

Talk about code development, features, specific bugzilla bugs, enhancements, patches, and other highly technical things.

Moderator: satrow

Forum rules
Please keep everything here strictly on-topic.
This board is meant for Pale Moon source code development related subjects only like code snippets, patches, specific referenced Bugzilla bugs, mercurial, etc.

This is not for tech support! Please do not post tech support questions in the "Development" board!
Please make sure not to use this board for support questions. Most "bug reports" do not belong in this board and should initially be posted in Community Support or other relevant support boards.

Please keep things on-topic as this forum will be used for reference for Pale Moon development. Expect topics that aren't relevant as such to be moved or deleted.
User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 21199
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Users of the unstable version: please note

Postby Moonchild » Mon, 04 Sep 2017, 09:51

Because of a temporary misconfiguration of the unstable builds, it is possible that you are not getting updates automatically any longer for the unstable builds.
This is caused by a tightening of the certificate check when using the internal updater, which is needed in this day and age where anyone and their dog can get a valid SSL certificate mis-issued on domains ({{snide remark about Let's Encrypt! removed}}). The flag to check was enabled before the credentials to check were updated, and a build was triggered in-between those two commits.

Please check if you are being offered updates (help -> about) if your build date is 2017-09-02 or before. If not, go into about:config, and temporarily set app.update.cert.checkAttributes to false, get today's update, then set it back to true.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"The wisest men follow their own direction." - Euripedes

Latitude
Astronaut
Astronaut
Posts: 550
Joined: Mon, 21 Mar 2016, 18:28

Re: Users of the unstable version: please note

Postby Latitude » Mon, 04 Sep 2017, 15:01

Moonchild wrote:This is caused by a tightening of the certificate check when using the internal updater


So, this is the latest change on internal updater codebase?

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 21199
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Re: Users of the unstable version: please note

Postby Moonchild » Tue, 05 Sep 2017, 08:42

It's the most recent change made to the internal updater system, yes. Why do you ask?
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"The wisest men follow their own direction." - Euripedes

User avatar
Moonchild
Pale Moon guru
Pale Moon guru
Posts: 21199
Joined: Sun, 28 Aug 2011, 17:27
Location: 58.5°N 15.5°E
Contact:

Re: Users of the unstable version: please note

Postby Moonchild » Fri, 27 Oct 2017, 00:15

Important: if you have updated the browser today to an unstable version of 2017-10-26, you may be stuck on a version that doesn't get automatic updates because of the change of infra and some unexpected Mozilla-isms in MAR generation.

You need to check the following:

  • Go to about:config and check the value of "app.update.channel"
  • If it is set to "unstable", you're good. Fast forward past the other points ;)
  • If it is set to "default", you're on a limbo version. You need to do the following:
    1. Exit the browser.
    2. Go to the folder where you installed the browser (application folder) or in case of the portable, go to Bin\Palemoon
    3. Go to defaults\pref\ inside that folder
    4. Edit the file "channel-prefs.js" and change the value of "default" to "unstable". Save.
    5. Start the unstable Pale Moon version and go to your about box. You should have an update available.
    6. Update! You're done.

Note that just changing the pref in about:config will not work (another Mozilla-ism getting in the way). You must edit the file as indicated to get out of limbo.
Improving Mozilla code: You know you're on the right track with code changes when you spend the majority of your time deleting code.

"The wisest men follow their own direction." - Euripedes


Return to “Development (discussion)”

Who is online

Users browsing this forum: No registered users and 1 guest