Puppy Linux Discussion Forum

Mike Walsh · Joined: 28 Jun 2014 Posts: 2630 Location: King's Lynn, UK.

***NEW VERSION***

Evening, everybody.

The new version of PepperFlash was released this afternoon. 32- & 64-bit versions of 25.0.0.171 are now available. Link as in post #1. Help yourselves to whatever you need.

Don't forget, there is now a .pet available to upgrade Pepper in 64-bit Iron.

-----------------------------------------------------------------------------------------

No need to manually upgrade in Chrome from version 54 onwards.....it's now handled internally by the browser's built-in updater, and upgrades all by itself. Smile

See the Chrome SFS thread for details.

Mike. Wink

musher0 · Posted: Tue 06 Jun 2017, 23:31 Post subject:

Hello, Mike_Walsh.

I just installed your latest PepperFlash, for Vivaldi: works great!

Many thanks!

Mike Walsh · Joined: 28 Jun 2014 Posts: 2630 Location: King's Lynn, UK.

Hi, musher0.

Now you've got me wondering... I don't produce one specifically for Vivaldi, so,er.....just out of curiosity, which one did you use?

Mike. Wink

musher0 · Posted: Wed 07 Jun 2017, 11:38 Post subject:

musher0 · Posted: Wed 07 Jun 2017, 23:44 Post subject:

Hello again, MIke.

BTW, I just updated my Vivaldi to v. 1.9, and
your pet works with the just out Vivaldi 1.9
as well as with the older guy, Vivaldi 1.7.

Mike Walsh · Joined: 28 Jun 2014 Posts: 2630 Location: King's Lynn, UK.

Morning, musher0.

Yes, that's the thing I realised quite a while back, when I first started researching the subject for this thread. Ever since Google dropped the NPAPI plug-in interface, and made the 'Pepper' PPAPI one standard for Chrome, that interface hasn't changed.

The very first all-Pepper releases of Chrome (around version 25 or 26.....and we're currently approaching version 60) will still work with the newest releases of the Pepper plug-in. I have version 26 of Chrome running in Lucid 5.2.8.7 (the newest version that will still run in it, because of the age of the glibc), and it, too, is currently using 25.0.0.171.....despite the fact that it originally used version 12-something-or-other.

It's not much, but it does allow you to keep at least one attack vector closed... As the saying goes, 'Every little bit helps'!

Mike. Wink

Mike Walsh · Joined: 28 Jun 2014 Posts: 2630 Location: King's Lynn, UK.

***NEW VERSION***

Afternoon, all.

The new version of PepperFlash was released this morning. 32- & 64-bit versions of 26.0.0.126 are now available. Link as in post #1. Help yourselves to whatever you need.

Don't forget, there is now a .pet available to upgrade Pepper in 64-bit Iron.

-----------------------------------------------------------------------------------------

No need to manually upgrade in Chrome from version 54 onwards.....it's now handled internally by the browser's built-in updater, and upgrades all by itself. Smile

See the Chrome SFS thread for details.

-----------------------------------------------------------------------------------------

I've fixed a long-standing problem with the 64-bit Chromium PepperFlash .pets. Since Chromium is the only one out of these that installs to /usr/lib, that means /usr/lib64 in these versions. Tahr64 has a sym-link from /usr/lib64 to /usr/lib, so it wouldn't make any difference.....but Slacko64 doesn't, so the location needs to be correct. I don't know about Xenial; I assume it's the same as Tahr. Can anyone confirm this, please?

Pepper now installs into /usr/lib64/Chromium/PepperFlash. All this time, and nobody's said anything..... (*shakes head*)

Curiously, Iron wants Pepper in /usr/lib, regardless of architecture. A query for the SRWare devs, perhaps... Razz

Mike.