>>
>> Or any other solution that achieves this result :-)
>
>That exists:
>update-flashplugin-nonfree --status
>update-flashplugin-nonfree --install
>
>Regards,
>Bart Martens
Bart, what you could do is change the exit status of your script to non-zero,
when "--quiet --status" does find a newer version.
That way we can make use of this feature in a daily cronjob.
I have to admit flash-plugin is really going down the drain now, which makes it
more
important to have an automated way for daily checks and possibly disable it
altogether
with a new switch called update-flashplugin-nonfree --disable. That switch
could simply
move the alternatives symlink to a an empty dumyfile and give that one the
highest
priority, as long it's not safe/desirable to use the current exploited and
yet-to-be-fixed version.
--status should of course reflect a "disabled" state.
We would however have to check how the browser reacts on that dumyfile ...
what's a safe way to disable a plugin and still have reference to
it as "beeing there, but disabled?
