search for: librhythmbox

...eamer. I think for anything that is a plugin, I think the browser should ask the user. That would make browser fingerprinting more difficult. One of the plugins though that is detected is from rhythmbox. I didn't even know there was a rhytmbox plugin for firefox. /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so It is part of the core rhythmbox package. I certainly have no need for it, and I doubt very many people do. It seems to me that maybe that plugin should be part of a sub-package to rhythmbox rather than rhythmbox itself, strictly from a security perspective so that if...

While doing a browser fingerprinting survey, I was quite surprised to see I actually have a FireFox plugin installed. The culprit is /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so It appears that whoever maintains the rhythmbox RPM has chosen not to package the browser plugin separately like it probably should be. So if I have the rhythmbox RPM installed, I have the plugin. This is rather worrisome because I can find no trace of the plugin in th...

...> > If you use a central Mozilla autoconfig file setup - see, for example: > > > <https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment#Configuration> > > then you can use the following line to disable this plug-in: > > lockPref("plugin.state.librhythmbox-itms-detection-plugin", 0); > > (and similar lines to disable any other plug-in) > > James Pearson With all the talk about deleting a packaged file or rebuilding a base package, I'm surprised no one has noticed this solution. The above is most likely the best solution. Easy...

On Wed, Nov 02, 2016 at 09:37:03PM -0700, Alice Wonder wrote > While doing a browser fingerprinting survey, I was quite surprised to > see I actually have a FireFox plugin installed. > > The culprit is > > /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so > > It appears that whoever maintains the rhythmbox RPM has chosen not to > package the browser plugin separately like it probably should be. So if > I have the rhythmbox RPM installed, I have the plugin. > > This is rather worrisome because I can find...

Walter Dnes wrote: > > How about manually... > > sudo rm /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so > > You'll have to do it each time you update rhytmbox. ... or create a very simple RPM that just has a '%triggerpostun' script that removes that file each time rhythmbox is updated James Pearson

Alice Wonder wrote: > While doing a browser fingerprinting survey, I was quite surprised to > see I actually have a FireFox plugin installed. > > The culprit is > > /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so > > It appears that whoever maintains the rhythmbox RPM has chosen not to > package the browser plugin separately like it probably should be. So if > I have the rhythmbox RPM installed, I have the plugin. > > This is rather worrisome because I can find no...

...:28 AM, Phil Wyett wrote: > On Wed, 2016-11-02 at 21:37 -0700, Alice Wonder wrote: >> While doing a browser fingerprinting survey, I was quite surprised to >> see I actually have a FireFox plugin installed. >> >> The culprit is >> >> /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so >> >> It appears that whoever maintains the rhythmbox RPM has chosen not to >> package the browser plugin separately like it probably should be. So if >> I have the rhythmbox RPM installed, I have the plugin. >> >> This is rather worrisom...

On Wed, 2016-11-02 at 21:37 -0700, Alice Wonder wrote: > While doing a browser fingerprinting survey, I was quite surprised to > see I actually have a FireFox plugin installed. > > The culprit is > > /usr/lib64/mozilla/plugins/librhythmbox-itms-detection-plugin.so > > It appears that whoever maintains the rhythmbox RPM has chosen not to > package the browser plugin separately like it probably should be. So if > I have the rhythmbox RPM installed, I have the plugin. > > This is rather worrisome because I can find...

...central Mozilla autoconfig file setup - see, for example: >> >> >> <https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment#Configuration> >> >> then you can use the following line to disable this plug-in: >> >> lockPref("plugin.state.librhythmbox-itms-detection-plugin", 0); >> >> (and similar lines to disable any other plug-in) >> >> James Pearson > > With all the talk about deleting a packaged file or rebuilding a base > package, I'm surprised no one has noticed this solution. The above is > mo...

...see, for example: >>> >>> >>> <https://developer.mozilla.org/en-US/Firefox/Enterprise_deployment#Configuration> >>> >>> >>> then you can use the following line to disable this plug-in: >>> >>> lockPref("plugin.state.librhythmbox-itms-detection-plugin", 0); >>> >>> (and similar lines to disable any other plug-in) >>> >>> James Pearson >> >> With all the talk about deleting a packaged file or rebuilding a base >> package, I'm surprised no one has noticed this sol...

On Thu, January 22, 2015 12:27, Frank Cox wrote: > On Thu, Jan 22, 2015 at 09:36:24AM -0500, James B. Byrne wrote: >> If one has already done all that and, following the most recent FF update, all that is displayed is a video window with the Flash >> logo/Button in the middle. And regardless of how many times one clicks on said button no video will show or sound will emit, what