Confirmed users
920
edits
Plugins:PluginDirectory/HowPluginDetectionWorks: Difference between revisions
Plugins:PluginDirectory/HowPluginDetectionWorks (view source)
Revision as of 14:35, 19 February 2010
, 19 February 2010→Version is not directly exposed
LesOrchard (talk | contribs) |
LesOrchard (talk | contribs) |
||
| Line 75: | Line 75: | ||
And, what's worse: Some plugins don't include a version number at all, neither in the the name nor description. (eg. Adobe Acrobat Reader has often presented this difficulty.) In this case, there's not much we can do besides shrug | And, what's worse: Some plugins don't include a version number at all, neither in the the name nor description. (eg. Adobe Acrobat Reader has often presented this difficulty.) In this case, there's not much we can do besides shrug | ||
and report the version as undetectable. | and report the version as undetectable. | ||
Our technique of last resort is to investigate custom hacks per-plugin to dig up version-related details. This tends to involve things like embedding a sample instance of the plugin and probing it for information. But, this can be very inefficient - and in the case of plugins with known vulnerabilities, can expose the user to the very crashes and security problems that the plugin detection is meant to warn about. | |||
On the bright side, Firefox 3.6 and above ''does'' offer a version property in | On the bright side, Firefox 3.6 and above ''does'' offer a version property in | ||