[SOLVED] CentOS 6 - Seamonkey - Your copy is old and probably has known security flaws

yenn · 09-29-2016, 07:23 AM

I'm using Seamonkey from EPEL as my primary browser and every time it starts, it shows red warning (see picture)

Code:

Your copy of seamonkey is old and probably has known security flaws

The thing is, I'm using latest version 2.40 - checked both by seamonkey website, yum and Seamonkey itself.

Code:

# yum info seamonkey
Available Packages
Name        : seamonkey
Arch        : x86_64
Version     : 2.40
Release     : 2.el6
Size        : 55 M
Repo        : epel
Summary     : Web browser, e-mail, news, IRC client, HTML editor
URL         : http://www.seamonkey-project.org
License     : MPLv2.0
Description : SeaMonkey is an all-in-one Internet application suite. It includes
            : a browser, mail/news client, IRC client, JavaScript debugger, and
            : a tool to inspect the DOM for web pages. It is derived from the
            : application formerly known as Mozilla Application Suite.

Even if I click on 'Check for updates' button to get rid of this warning, nothing happens.

Is there a newer version of seamonkey or is there some problem with my profile? I also use the same version of Seamonkey on Slackware and don't see this warning.

malekmustaq · 09-30-2016, 12:33 AM

Quote:

Is there a newer version of seamonkey

So far 2.4 is the latest. Try download and run a seamonkey GTK binary of same version, find out if same warning appears. In my case it does not appear.

Quote:

or is there some problem with my profile?

If you suspect your profile has issue try run it as new-profile. It is easily done Tools-->Switch profile... >> Create new, quit seamonkey and launching again will offer you to choose among profiles.

Hope that helps. Good luck and enjoy!

m.m.

bathory · 09-30-2016, 07:01 AM

Maybe a RHEL based distros bug.
Have a look at this post for a workaround

yenn · 09-30-2016, 08:30 AM

Quote:

Originally Posted by bathory

Maybe a RHEL based distros bug.
Have a look at this post for a workaround

Definitely bug in RHEL based distro binaries.

I tried binaries from mozilla and haven't encounter this bug with clean profile. Nevertheless, linked workaround helped, thanks!

By the way, it's nice to see that among all distros here at LQ, Slackers came to rescue :-)