This bug has been fixed in pepperflashplugin-nonfree 1.8.3+nmu1 in Debian on 2017-01-14, and the fix landed in 1.8.3+nmu1ubuntu1 in Ubuntu Zesty (the current development release) on 2017-01-22. The PPAPI Flash plugin is now downloaded from Adobe rather than Google. One still has to run the provided update-pepperflashplugin-nonfree to update it from time to time.
I'm marking the bug as Fix Released (in the development release).
The package is still broken in the published releases: Trusty, Xenial, Yakkety. Is it worth requesting Stable Release Updates? It would qualify, since the bug comes from a web service change that makes the package stop working, and exposes the user to Flash vulnerabilities.
I also still believe, like I said in comment 32, that this package offers no advantage over adobe-flashplugin, besides being in multiverse rather than in partner. Unless that last point is important (independence from Adobe/Canonical, perhaps?), dropping the package from Zesty seems more appropriate to me. If this has to be done before FeatureFreeze, there's only a couple days left. Gunnar, do you have the authority to do that? Also, did you get feedback from Chris Coulson?
This bug has been fixed in pepperflashplug in-nonfree 1.8.3+nmu1 in Debian on 2017-01-14, and the fix landed in 1.8.3+nmu1ubuntu1 in Ubuntu Zesty (the current development release) on 2017-01-22. The PPAPI Flash plugin is now downloaded from Adobe rather than Google. One still has to run the provided update- pepperflashplug in-nonfree to update it from time to time.
I'm marking the bug as Fix Released (in the development release).
The package is still broken in the published releases: Trusty, Xenial, Yakkety. Is it worth requesting Stable Release Updates? It would qualify, since the bug comes from a web service change that makes the package stop working, and exposes the user to Flash vulnerabilities.
I also still believe, like I said in comment 32, that this package offers no advantage over adobe-flashplugin, besides being in multiverse rather than in partner. Unless that last point is important (independence from Adobe/Canonical, perhaps?), dropping the package from Zesty seems more appropriate to me. If this has to be done before FeatureFreeze, there's only a couple days left. Gunnar, do you have the authority to do that? Also, did you get feedback from Chris Coulson?