MX 17/18 Repository: The Pale Moon Browser Thread

Message
Author
User avatar
MX-16_fan
Posts: 331
Joined: Mon Feb 13, 2017 12:09 pm

Re: MX 17 Repository: The Pale Moon Browser Thread

#21 Post by MX-16_fan »

@vksan:
vksan wrote:MX-16_fan -

>Master Password and passwords

I remember researching this several years ago. (I realize we are discussing Pale Moon ...) Back in the day, one needed a master password to encrypt the passwords. This is from 2009:

https://luxsci.com/blog/master-password ... rbird.html

Mozilla's page about the Master Password, updated in 2018:

http://kb.mozillazine.org/Master_password

Pale Moon forum entry by Moonchild (developer of Pale Moon), dated 2016:

https://forum.palemoon.org/viewtopic.ph ... ted#p81494

A very recent discussion about the Master Password on the Pale Moon forums (note Moonchild has included a link to a bug report and the bug report contains a link to Mozilla's bug report):

https://forum.palemoon.org/viewtopic.php?f=4&t=18643

Thanks! What's the bottom line of all this? Greetings, Joe

User avatar
Stevo
Developer
Posts: 12774
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The Pale Moon Browser Thread

#22 Post by Stevo »

Pale Moon has been updated to 27.8.2 in the main repository. This is a security update.

Changes/fixes:

Privacy fix: prevented update checks for the default theme.
Added a user-agent override for Dropbox to improve compatibility with their service.
Fixed an issue with mouseover handling related to (CVE-2018-5103). DiD
Disabled the Mac OSX Nano allocator. DiD
Fixed (CVE-2018-5129) OOB Write.
Updated the lz4 library to 1.8.0 to solve potential issues. DiD
Fixed (CVE-2018-5137) Path traversal on chrome:// URLs
Fixed several memory safety an synchronicity hazards.

DiD This means that the fix is "Defense-in-Depth": It is a fix that does not apply to a (potentially) actively exploitable vulnerability in Pale Moon, but prevents future vulnerabilities caused by the same code, e.g. when surrounding code changes, exposing the problem, or when new attack vectors are discovered.

User avatar
Stevo
Developer
Posts: 12774
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The Pale Moon Browser Thread

#23 Post by Stevo »

The new 27.9.0 release has now landed in the main repository! Changes are:

* New release:
- Fixed a number of spec compliance issues in our media subsystem.
- Added a trailing slash to referrers when policy is set to fix some web
compatibility issues.
- Fixed the property order in Object.getOwnPropertyNames(string) and others
for web compatibility.
- Updated RegExp(RegExp object, flags) to the ES6 standard specification.
- Changed the embedded font from the no longer free EmojiOne to the
open-licensed Twemoji (with additional fixes). This also further extends
unicode support to Unicode 10 emoji(s). Please note that as a result, color
emoji(s) will look different than before.
- Adjusted some things in our memory allocator code to provide, among other
things, better allocation alignment on Windows.
- Made the attempt to migrate people from the old sync server domain name to
the current one more aggressive. We will be retiring the old
pmsync.palemoon.net Sync server address shortly to remove the need for us
to maintain a security certificate for it; this preference migration should
automatically put everyone on the correct server address when upgrading.
- Made reading of the sessionstore synchronous, to speed up startup and
prevent the homepage from being loaded when restoring a session.
- Added a fix to switch to the correct window/tab when a web notification
is clicked.
- Changed the placeholder text to not include "Search" when all search
functions from the address bar are disabled.
- Enabled the use of Skia for canvas on Linux and OSX.
- Worked around a potential cause for some non-standard bitmapped fonts
ending up with incorrect line heights (I'm looking at you, Noto fonts!).
- Added a workaround for incorrectly-encoded JPEG-XR images with planar
alpha. Ultimately, the jxrlib reference implementation should be fixed to
encode according to spec.
- Aligned XCTO:nosniff allowed script MIME types with the updated spec.
- Improved the logic for storing vector images in the surface cache.
- Fixed character set handling for XMLHttpRequests.

User avatar
Gordon Cooper
Posts: 965
Joined: Mon Nov 21, 2011 5:50 pm

Re: MX 17 Repository: The Pale Moon Browser Thread

#24 Post by Gordon Cooper »

27.9 has not appeared yet on the UT repo. Not to worry, will try again tomorrow.

Edit: 'Tis now tomorrow and have got 27.9. Thanks.
Backup: Dell9010, MX-19_B2, Win7, 120 SSD, WD 232GIB HD, 4GB RAM
Primary :Homebrew64 bit Intel duo core 2 GB RAM, 120 GB Kingston SSD, Seagate1TB.
MX-18.2 64bit. Also MX17, Kubuntu14.04 & Puppy 6.3.

User avatar
Stevo
Developer
Posts: 12774
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The Pale Moon Browser Thread

#25 Post by Stevo »

Updated to 27.9.1 in the main repo.
* New upstream maintenance update:
- Removed the unused/incomplete places protocol handler.
- Worked around an issue with MSE media without a Track ID. This should help
with the playability of some live streams.
- Ported across jemalloc improvements from UXP.
- Ported across cairo mutex improvements from UXP.
- Added support for FFmpeg 4.0/libavcodec 58.
- Added a fix for Windows 10's "isAlpha()" not being what one would expect
in v1803.

User avatar
fehlix
Developer
Posts: 10310
Joined: Wed Apr 11, 2018 5:09 pm

Re: MX 17 Repository: The Pale Moon Browser Thread

#26 Post by fehlix »

Stevo wrote:Updated to 27.9.1 in the main repo.
On mx17.1 and antiX17.1 I do get for upgrade/install palemoon:i386

Code: Select all

The following packages have unmet dependencies:
 palemoon : Depends: libfontconfig1 (>= 2.12.6) but 2.11.0-6.7+b1 is to be installed
I did send another post probably within the wrong thread about this issues
here: viewtopic.php?f=57&t=39874&start=930#p446504
Gigabyte Z77M-D3H, Intel Xeon E3-1240 V2 (Quad core), 32GB RAM,
GeForce GTX 770, Samsung SSD 850 EVO 500GB, Seagate Barracuda 4TB

User avatar
Gordon Cooper
Posts: 965
Joined: Mon Nov 21, 2011 5:50 pm

Re: MX 17 Repository: The Pale Moon Browser Thread

#27 Post by Gordon Cooper »

Am running 27.9.1 on 64 bit system with all dependencies met. Uses libfontconfig1 2.13.0.4-MX17+1
Backup: Dell9010, MX-19_B2, Win7, 120 SSD, WD 232GIB HD, 4GB RAM
Primary :Homebrew64 bit Intel duo core 2 GB RAM, 120 GB Kingston SSD, Seagate1TB.
MX-18.2 64bit. Also MX17, Kubuntu14.04 & Puppy 6.3.

User avatar
Stevo
Developer
Posts: 12774
Joined: Fri Dec 15, 2006 8:07 pm

Re: MX 17 Repository: The Pale Moon Browser Thread

#28 Post by Stevo »

I just sent up the fixed MX 17 i386 version of PM, but you can get it early here: Edit, incorrect versioning...will get the correct version up in an hour or so.
Last edited by Stevo on Thu May 10, 2018 3:26 pm, edited 1 time in total.

User avatar
anticapitalista
Developer
Posts: 4160
Joined: Sat Jul 15, 2006 10:40 am

Re: MX 17 Repository: The Pale Moon Browser Thread

#29 Post by anticapitalista »

stevo - the new deb is labelled mx15.
anticapitalista
Reg. linux user #395339.

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - lean and mean.
https://antixlinux.com

linwinux

Re: MX 17 Repository: The Pale Moon Browser Thread

#30 Post by linwinux »

Hi guys, not a lot of time todyay, so just a quick note (yeah right, right?) ;)

Remember that weird, possibly screensaver related issue I mentinoed awhile ago ... the one that triggers a funky looking desktop with a huge 150px+ border around everything and missing window decorations ... a problem which corrects itself inexplicably after a little while ... ???

PALEMOON is the culprit. If my system runs stable without any hitches for a few days, while using nothing but FF and keeping it open (minimized) on the screen, followed by then opening Palemoon .... bamm, that weird crash thingie whatever it is, occurs. I can duplicate it without a problem and there does appear an x-screensaver message of sorts with 2 errors on the screen. As stated, I can duplicate this and so far only palemoon has been able to cause this on my machine. I took photos of the screen, just don't have time to upload them today.

No, please don't advise not to use a screensaver. If any fix on MX requires the lack of using a screensaver ... then screensavers should be removed from MX. That would be the correct solution, instead of implying that something which is used by countless millions of people, should not be used anymore. I'll be back tomorrow to post those photos. Screenshots of the full problem are impossible because every time that the mouse is clicked or a keyboard key tapped, the screen changes again ... eventually returning to normal. Happy Fathersday for all of you Dads out there (in Germany) !!! :happy:

Locked

Return to “Package Requests/Status - MX 17/18”