Arch Linux User Repository

As far as I'm aware that is only applicable to the web-browser plugin version. Standalone/Projector should still work fine. At the very least 32.0.0.453 which is the last update I pushed is still working perfectly fine here. (haven't build/updated to 465 yet so I can't say anything about that)

Since 371 is also one I pushed I can try and see if it's still in a build cache of mine but don't keep your hopes up (and regardless; it really shouldn't matter for the standalone/projector version)

EDIT: Last build cache for that version was removed 6 months ago so I no longer have it and my backups for those only go back 1 month.

EDIT2: I just see that the date for the time bomb wasn't 01-01-2021 but a tad later this month so the projector might start failing later.

EDIT3: If the standalone/projector does indeed also end up containing said time-bomb, the next best solution I can think of is to use Ruffle browser addon/extension to play your flash content using your browser.

I maintain the latest built package at:

https://github.com/frealgagu/archlinux.flashplayer-standalone/releases/

The validity check fails. What do I do?!?

When the validity check fails for the downloaded file, Adobe most likely released a new version.
Please flag it out-of-date if that is indeed the case (check the Upstream URL) instead of dropping a comment or doing nothing.

Why does this happen?

Adobe doesn't actually have the version in the filename/URL. When the build process downloads the file, it is stored locally with the version number in the name but the upstream download URL is always the same; https://fpdownload.macromedia.com/pub/flashplayer/updaters/32/flash_player_sa_linux.x86_64.tar.gz

The result of this is that when Adobe releases a new version, this file on their server is replaced and thus the file downloaded from that URL during the build process will no longer match the checksum that is recorded in the PKGBUILD.

@carloza; see the earlier messages on this subject. Making the update to the AUR as we speak.

This package show the following error

==> Validando los archivos source con sha256sums...
    flashplayer-standalone-32.0.0.414.tar.gz ... HA FALLADO
==> ERROR: ¡Uno o más archivos no superaron el control de validación!
error descargando fuentes: flashplayer-standalone

@vbs when that happens please flag it instead.

Here we go again:

==> Validating source files with sha256sums...
    flashplayer-standalone-32.0.0.270.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

@lowkrsbhs No, this is caused because a new version 32.0.0.238 is available (and the artifact in download page is replaced). I'll update ASAP.

@lowkrsbhs No, this is caused because a new version 32.0.0.238 is available (and the artifact in download page is replaced). I'll update ASAP.

==> Validating source files with sha256sums... flashplayer-standalone-32.0.0.192.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check!

Tried to download it many times, but did not work. I think the update on 6/11/19 made it break?

Adobe doesn't actually have the version in the filename, that is something the PKGBUILD does when storing it locally. The upstream URL is always the same (fwiw; https://fpdownload.macromedia.com/pub/flashplayer/updaters/32/flash_player_sa_linux.x86_64.tar.gz). The checksum change indicates a new version release. Doesn't seem like they updated the main page with that information yet, but we're on version 32.0.0.142 now. I'll update it in a bit.

EDIT: Updated. And so did Adobe; 02/12/2019 – Updated debugger and standalone versions of Flash Player. These versions contain fixes for critical vulnerabilities identified in Security Bulletin APSB 19-06. The latest versions are 32.0.0.142 (Win, Mac & Linux). All users are encouraged to update to these latest versions.

Checksum verification fails (again):

==> Validating source files with sha256sums...
    flashplayer-standalone-32.0.0.114.tar.gz ... FAILED
==> ERROR: One or more files did not pass the validity check!

.. does upstream change the source package even without a version upgrade? Version number is in filename ...