MozillaZine

[SOLVED] SM 2.33.1 says Flash 11.2.202.468 is 11.2.202.460

Discussion of bugs in Seamonkey
Walter Dnes
 
Posts: 25
Joined: November 26th, 2004, 7:57 pm
Location: Greater Toronto, Canada

Post Posted July 2nd, 2015, 4:17 pm

Seamonkey is putting up warnings that the current version is vulnerable, and that I
need an update. I'm running Seamonkey 2.33.1 running 64-bit Gentoo on an 8-year-old Core 2 Duo.
"about:plugins" says...

File: libflashplayer.so
Path: /usr/lib64/nsbrowser/plugins/libflashplayer.so
Version: 11.2.202.460
State: Enabled (STATE_VULNERABLE_UPDATE_AVAILABLE)
Shockwave Flash 11.2 r202

...but, but, but I *KNOW* have 11.2.202.468 installed. And Gentoo agrees with me. Just to make sure there weren't multiple copies, I ran the command...

find / -name libflashplayer.so

and found ounly 1 copy. I went to Adobe's website, and downloaded the current linux x86_64 Flash. According to the Adobe website, it's 11.2.202.468. I ran "diff -bs" against my current libflashplayer.so and the one I extracted. They're byte-for-byte identical. I also ran...

"strings libflashplayer.so | grep 202"

4 of the lines returned were...

FlashPlayer_11_2_202_468_FlashPlayer
LNX 11,2,202,468
11.2.202.468
drm/%s/%s/%s/11.2.202.468%s

To summarize; I'm running Flash 11.2.202.468, but Seamonkey thinks it's 11.2.202.460, which triggers a vulnerability warning.
Last edited by Walter Dnes on July 2nd, 2015, 8:04 pm, edited 1 time in total.

barbaz
 
Posts: 1680
Joined: October 1st, 2014, 3:25 pm

Post Posted July 2nd, 2015, 5:02 pm

Try: completely quit SeaMonkey, then delete pluginreg.dat from your profile folder?
*Always* check the changelogs BEFORE updating that important software!

Walter Dnes
 
Posts: 25
Joined: November 26th, 2004, 7:57 pm
Location: Greater Toronto, Canada

Post Posted July 2nd, 2015, 8:02 pm

Thank you very much. That worked. I had already tried quitting all instances of Seamonkey
("killall seamonkey")
and restarting, but that wasn't sufficient. What finally worked was...

killall seamonkey
cd ~/.mozilla
find "." -name pluginreg.dat -delete

I have 19 separate profiles, to isolate various activities. That's why I used "find" instead of deleting manually. There are a couple of forums I frequent that randomly peg a CPU core to 100% (bleeping javascript, and they won't function without it). Having separate profiles allows me to kill the offending browser without killing everything else. I use "top c" in an xterm to find the offenders. "about:plugins" now shows...

File: libflashplayer.so
Path: /usr/lib64/nsbrowser/plugins/libflashplayer.so
Version: 11.2.202.468
State: Enabled
Shockwave Flash 11.2 r202

James
Moderator

User avatar
 
Posts: 27379
Joined: June 18th, 2003, 3:07 pm
Location: Made in Canada

Post Posted July 3rd, 2015, 4:06 pm

One trick that can help get SeaMonkey/Firefox to detect the new version of Flash on Linux is to type about:plugins in Location (address) bar.

Walter Dnes
 
Posts: 25
Joined: November 26th, 2004, 7:57 pm
Location: Greater Toronto, Canada

Post Posted July 3rd, 2015, 6:24 pm

James wrote:One trick that can help get SeaMonkey/Firefox to detect the new version of Flash on Linux is to type about:plugins in Location (address) bar.

I did exactly that in the first post of this thread, and it was showing .460 when it should've been .468. This was after killing all seamonkey instanecs and re-starting. barbaz suggested zapping the pluginreg.dat files. That hits Seamonkey over the head and forces it to do a fresh read on what's available.

James
Moderator

User avatar
 
Posts: 27379
Joined: June 18th, 2003, 3:07 pm
Location: Made in Canada

Post Posted July 4th, 2015, 1:23 am

hmm sorry I missed that. This trick does work for me if I manually placed a new libflashplayer.so in ~ .mozilla/plughins/ folder while SeaMonkey/Firefox was still running even.

Walter Dnes
 
Posts: 25
Joined: November 26th, 2004, 7:57 pm
Location: Greater Toronto, Canada

Post Posted July 4th, 2015, 11:08 pm

One non-standard thing that I do may be related to this. I tend to have multiple tabs open, over a few browser instances, following several threads on a few forums. Rather than exiting Seamonkey the standard way, I use the linux "kill" command to shut down the browser instance. When I restart that profile, Seamonkey offers to "restore the session". I love it, because I usually have several threads open in some forums, and it takes me back to exactly where I was in those threads. I wonder if it takes "restore the session" too literally, and restores the values that it had read before in about:plugins. It seems that removing pluginreg.dat is the only thing drastic enough to force a re-read of plugins for my system.

therube

User avatar
 
Posts: 19040
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted July 5th, 2015, 5:18 am

I use the linux "kill" command to shut down the browser instance.

Hardly appropriate, I would think.
(Appears default might be SIGTERM, which might not be so bad, but nonetheless.)

Seamonkey offers to "restore the session"

Just lucky, I would think.

BTW, Session Restore is a feature of SeaMonkey.
That it happens to work they way you're forcing things, plain luck IMO.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

therube

User avatar
 
Posts: 19040
Joined: March 10th, 2004, 9:59 pm
Location: Maryland USA

Post Posted July 5th, 2015, 5:28 am

How appropriate, gracefully quit Firefox from the command line (even if slightly ancient).
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript

Return to SeaMonkey Bugs


Who is online

Users browsing this forum: No registered users and 2 guests