hi boys
changing the pluginreg.dat doesn't change the security hole.
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-5470
** Information type changed from Public to Private Security
** CVE added: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2012-1775
** CVE added: h
Same issue here. Removing the pluginreg.dat fixes it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047766
Title:
Mozilla warns browser-plugin-vlc is out-of-date
To manage notifications about this
I figured it out. Mozilla stores information about each plugin in
path/to/profile/pluginreg.dat, and this held the old version of VLC. I
think the reason my Firefox (and SeaMonkey) browser didn't update this
is it checks the lastModified time of the plugin file at startup.
Although I have an upda
My browsers seem to be caching the wrong plugin version. If I start my browser
with a new profile (-P -no-remote), it reports
Version 2.0.4 Twoflower, copyright 1996-2011 VideoLAN and Authors
and plugincheck is happy.
So the sequence was
* Install VLC 2.0 and browser-plugin-vlc package; browse
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: npapi-vlc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047766
Title:
** Package changed: vlc (Ubuntu) => npapi-vlc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1047766
Title:
Mozilla warns browser-plugin-vlc is out-of-date
To manage notifications about thi
