SCIENTIFIC-LINUX-USERS Archives

March 2016

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
Mailing list for Scientific Linux users worldwide <[log in to unmask]>
Date:
Wed, 23 Mar 2016 08:23:52 +0000
Reply-To:
Andrew C Aitchison <[log in to unmask]>
Message-ID:
Subject:
From:
Andrew C Aitchison <[log in to unmask]>
Content-Type:
multipart/mixed; boundary="-1463774976-2063885161-1458721434=:24521"
In-Reply-To:
MIME-Version:
1.0
Comments:
To: Franchisseur Robert <[log in to unmask]> cc: [log in to unmask]
Parts/Attachments:
text/plain (1129 bytes)

> -- Le (On) 2016-03-22 -0700 à (at) 10:03:03 Keith Lofstrom écrivit (wrote): --
>
>> Is there a way to TURN OFF Firefox "flash is insecure" nagging,
>> or FORCE "Always Activate" when it is grayed out in about:addons?

On Wed, 23 Mar 2016, Franchisseur Robert wrote:
>       Hello,
>
>       I  had  the  same  issue and I put the following  line  in  my
>       ~/.bash_logout
>
>       \rm $HOME/.mozilla/firefox/XXXXXXXXX.default/pluginreg.dat
>
>       so  I  got  the  good version of  flash-plugin  without  doing
>       nothing more.

Keith, Franchisseur is right.
I especially like the idea of fixing pluginreg.dat in .bash_logout

The important thing when updating flash is to remove the old flash version
number from pluginreg.dat in *each* firefox profile.

I am, however, uneasy about simply removing the file completely, as
that removes all the user's plugin customizations; so if they have 
disabled any plugins they mayl be reenabled.
I haven't checked for a while, but it was once possible for users
to have their own plugin folder; removing pluginreg.dat would
unconfigure those plugins too.

-- 
Andrew C Aitchison				Cambridge, UK


ATOM RSS1 RSS2