I see little reason to patch the Chrome part of your setup if you keep a
(then entirely unsupported) Flash plug-in around that will be
accumulating security holes. 2020 it two years away - time to rewrite
the app using a supported, up-to-date technology.
- Bartosz
> <
https://www.chromium.org/flash-roadmap>). As far as I know, Flash is
> currently embedded into the browser via the PPAPI/Native-Client and
> therefore runs in a sandbox. In my current situation we have to ensure,
> that a large proprietary
> <
https://dict.leo.org/englisch-deutsch/proprietary> Flash Application
> can be used even after 2020 by their clients. The clients are the
> employees of that company. So we only need a local solution for the
> employees using the application internal. I thought about forking the
> chromium project, keeping the Flash part, while successively updating
> the other parts of the project to get the latest security patches etc.
> What are your suggestions on this topic? How will we be able to run our
> Flash Applications in Chromium after 2020? Is there already a project
> focusing on this? Are there other ways to keep Flash Player support?
> Maybe via configuration of Chromium?
>
> --
> --
> Chromium Discussion mailing list:
chromium...@chromium.org
> View archives, change email options, or unsubscribe:
>
http://groups.google.com/a/chromium.org/group/chromium-discuss
>