Can you give me some informations about what was vulnerable in VLC 2.0.6 ?Sorry people, this just shows that Mozilla people are stupid.
What is vulnerable is the VLC version and not the plugin, Mozilla should check VLC version and not plugin version.
If you are on 2.0.8 you are safe.
Yes.Or do you mean the checkmethod of Mozilla is not correct and if they check the version no warning would appear?
To avoid confusing users, I suggest you reconsider your policy for built-in version identification. When I install a 2.0.8 package, I expect the package to be 2.0.8 regardless of the detailed change history of individual files.Sorry people, this just shows that Mozilla people are stupid.
What is vulnerable is the VLC version and not the plugin, Mozilla should check VLC version and not plugin version.
If you are on 2.0.8 you are safe.
The version number of the web plugin is the version number of the web plugin. You can run version 2.0.6 of the web plugin on top of version 2.0.4 of the library (libvlc.dll) if you want. They are linked dynamically afterall. Similarly, you can keep using an old libvlc.dll and selectively update plugin DLLs and since security issues are almost always within plugins, some people do just that.To avoid confusing users, I suggest you reconsider your policy for built-in version identification.Sorry people, this just shows that Mozilla people are stupid.
What is vulnerable is the VLC version and not the plugin, Mozilla should check VLC version and not plugin version.
If you are on 2.0.8 you are safe.
This makes no sense whatsoever. The VLC installer is the combination of tens of different open-source packages, each with its own version number. Most of them are not even maintained by the VideoLAN team. Keeping the same master version number for all of them is essentially impossible.When I install a 2.0.8 package, I expect the package to be 2.0.8 regardless of the detailed change history of individual files.
Last I checked, Windows did not have the same version number in all of its DLLs either.After installing VLC 2.0.8, libvlc.dll and libvlccore.dll identify themselves as 2.0.6, not just npvlc.dll.
Not at the place you think it does.Mozilla reads the version in the DLL.
did you know Security is the prime concern with Firefox support.I regularly see issues with Adobe plugins on various versions of Windows when I update client machines
I do appreciate that Firefox support takes security as a prime concern, but when the plugin checker gets it wrong, then the plugin checker gets less trusted and ordinary users will be lost ... and let's face it, too many /ordinary/ users (the majority), have no idea that plugin checker even exists. The plugin check must be accurate, reliable and trustworthy.Putting Users in Control of Pluginsdid you know Security is the prime concern with Firefox support.I regularly see issues with Adobe plugins on various versions of Windows when I update client machines
Return to “VLC media player for Windows Troubleshooting”
Users browsing this forum: No registered users and 56 guests