In Firefox, I downloaded the new version for flashplayer cause it was recommanded.
I downloaded the *.tar.gz file.
After extract it give me a libflashplayer.so file.
I don't remember the place where to replace with the old one.

It can go in a couple of different places. I would delete whatever libflashplayer.so that you have in both /usr/lib/mozilla/plugins and /usr/lib/firefox/plugins. Then I would place your new file in /usr/lib/mozilla/plugins and restart firefox.

if you installed the old version from a package maybe you better install also the new in the same way: if can be useful I prepared a package (32bit only, as adobe is not releasing the x86_64 version anymore, for now) to upgrade my installations.

I created it from slackbuild.org script following the hints.
I got the right VERSION variable looking at the slackbuild: if you go in the folder in which you have the untarred libflashplayer.so just downloaded you can get the right value to use in the slackbuild like this
for the one downloaded now is 10.1_r82

Finally I put the libflashplayer.so in
/usr/lib/mozilla/plugins
the place where I found the previous one, I just replace the old one by the new.
I'm on slackware current 32 bits

:-/ NjB /

That's not a good idea really.
The only plugin that you should have in /usr/lib/mozilla/plugins should be libnullplugin.so.

All the others should be in your profile directory. Move all plugins in /usr/lib/mozilla/plugins, ~/.mozilla/plugins and ~/.mozilla/firefox/plugins (if you have these dirs) to your ~/.your_profile/plugins[*] directory and clear the other directories of all plugins, apart from usr/lib/mozilla/plugins which should have libnullplugin.so.

I have two firefox profiles: one is as a normal user and the other is a secure profile which I use for financial stuff. Since there are questions about flashplayer's security, I don't want that to be loaded by any pages when I am browsing in secure mode.

Indeed, the main point of my secure profile is that it has no add-ons/extensions/plugins etc.. It is just pure Firefox. The one exception to that rule is the noscript extension, since that increases my security.

It is also generally good to let each user decide for themselves which plugins they want and do not want.

* You may have your profile directory in the .mozilla directory, in which case put it in the plugins directory of your profile there. (when I create a profile, I prefer putting the directory simply in ~/ with a meaningful name).

1 members found this post helpful.

How Firefox and Thunderbird are going to find the new path for these plugins ??

;-/ NjB /

They find them automatically because it is your profile directory. It isn't, in fact, a "new" path.

[EDIT]
If you meant that you want to create new profiles and are wondering how Firefox knows what profile you want, then that is done by adding "-P profile-name" as a parameter to the firefox command. The first time you use it, it will go into profile manager mode and let you create the profile and, if you wish, the directory you want to create and use as the profile directory for that profile.

After that, always use the "-P profile-name" to indicate which profile you want to use and then it starts automatically without going into profile manager.

If you just have one profile for your user id, the -P parameter isn't necessary.

Then how will any non-mozilla browsers find the plugin? Do you expect them to search your mozilla profile in your home directory? Your solution is very, very specific for your usage case and not so much for everyone else. If you wish all of your users to be able to use the plugin then I see nothing wrong with using /usr/lib/mozilla/plugins, and I would repeatedly recommend placing plugins there.
There are questions about *every* package's security. Flash player 10.0 has a massive security hole but if you're using /usr/lib then you are obviously running 32-bit Slackware and should be using Flash 10.1, which has no such vulnerability. Of course both Firefox and Flash may have other vulnerabilities but using FlashBlock is probably a nicer solution then running two disparate Firefox profiles. It is your system, however, so I don't fault you there -- but telling *others* to avoid putting plugins in a standard location may bring problems later when they try to use a non-mozilla browser and cannot get Flash to work.
I dare say that, excluding certain plugins, Firefox is a much more vulnerable beast than 99% of its add-ons. Recently several vulnerabilities were disclosed for Firefox before 3.6.9, and of course they were only disclosed to CVE after being fixed (presumably to prevent an unfixed hole that someone could exploit). This also means it is very likely that there are tons of as-yet undisclosed/undiscovered vulnerabilities in Firefox, and I would say using Flash+FlashBlock is more then adequate to prevent any Flash-based problems while still maintaining cross-browser compatibility.

Why should they be using the plugins installed in Mozilla? what happens if you decide to remove mozilla? That will then impact all the other non-mozilla browsers.

Opera places its plugins in its own directories - that is good.

What you are suggesting is to create a nightmarish interdependence between programs that should not have any, or the least possible, interdependence.

Why should the Opera user be dependent upon what Mozilla has installed?

As I said before, it is better for the users themselves to decide which plugins they want.

I do have 10.1. Security is not about known vulnerabilities. It is about reducing possible vulnerabilities. If I don't need flash or the firefox extensions, why should I have them installed in my secure browser and thus increase the risk of possible vulnerabilities?

In short, the known vulnerabilities are not the ones you need to worry about. It is the unknown ones. So minimise them.

/usr/lib/mozilla/plugins is a standard directory that most browsers look for (Opera, virgin webkit browsers, Konqueror, ...). This may not agree with you but it is the truth. If you uninstall mozilla packages using removepkg it will remove the package while leaving the /usr/lib/mozilla/plugins directory because it contains files that did not exist in the original package. Removing all mozilla packages will not remove the flash plugin, and Opera, Konqueror, webkit browsers, the works will still be able to access and use the flash plugin. And if you decide to reinstall any mozilla browser it will also be able to find the flash plugin.

Your issues with security are fine; if you want to create the extra step, that's your prerogative. However, I stand by placing plugins in /usr/lib{64}/mozilla/plugins for the vast majority of users, along with installing FlashBlock if you are concerned about security.

On a multiuser system you want every single user to install Flash to their local directories for every single browser available? If you have a system with multiple real users, I'm sure this is not acceptable. I install plugins globally and addons locally.

Very pationated discution really.
My purpose in this thread was very simple.
I have a desktop with slackware 32, and mono user.
Once I had a message that I had to upgrade flashplayer,
So I downloaded it and extract the directory and found the *.so file.

So for me I need a standard path to put it as I am a single user.
It's good for me and I don't have any more upgrade message ;-)

But really the discution above was very instructive for me cause it open so much vision of things.

So Thank you All for the debat.

Respect :-/ NjB /

Just to say that I recently updated the flashplayer in my recently installed slackware 64 current for the video playing in Firefox 3.6.12
The driver was a specific one

Quote:

Flash Player "Square" Preview ReleaseThis page contains download information for the developer preview release of Adobe® Flash® Player "Square" (codename). Flash Player "Square" enables 64-bit and enhanced Internet Explorer 9 support.

The path was
/usr/lib64/mozilla/plugins/libflashplayer.so

NjB