Chromium v83 with pepper-flash **RUNS-AS-SPOT**

[peebee]

PepperFlash now 32.0.0.156

[peebee]

withdrawn

[OscarTalks]

Edit:- Quote including withdrawn link removed

Tried this in a fresh boot of ScPup 19.01+5 32bit
Throws a symbol lookup error and refuses to start (library mismatch?)
Tried installing slackware gtk+3 but didn't help.
Was just a quick test so maybe I did something wrong?

[peebee]

Was just a quick test so maybe I did something wrong?

My apologies - withdrawn - inadequate testing

Works on my latest build of LxPupSc but other builds probably need updating first....

[peebee]

For 32-bit LxPupSc and ScPup only ......... a Debian Sid build ............

chromium_73.0.3683.75-1+pepper_32.0.0.171_lxsc_spot.sfs

[peebee]

64-bit:
chromium64_73.0.3683.75+pepper_32.0.0.171_lx_spot.sfs

32-bit: not yet available

[pp4mnklinux]

The same problem happened to me, I want the latest Chrome and I couldn't find it, till I discovered a soft called "GetLatest64bitChromeVersion-MK11.pet" and now all becomes easy

Try it.

https://drive.google.com/open?id=1SlX74 ... c_u6xCq4Cn

For linux experts, it is child play. This is my long pending demand. I don't know why people are not taking up this task. I will be very happy if somebody provide latest chromium or Iron or google chrome browser for wary/racy.

[davids45]

G'day,

Updated to this Chromium-72-as-spot from a fine and spotless Chromium 59.

Where is the config data now held for Chromium?

In v59, I had it linked from each Pup's /root/.config/chromium/ to a common directory on my data partition so all Pups have the same profile data etc. for chromium (screenshot shows a Pup's /root/.config/ with many configs (icons with corner arrows) linked back to data partition directories to allow sharing of just one profile for each application between all Pups on the computer).

But not now as I cannot find where this important information is now stored by v72.

Thanks for any help, or should I just stay with v59?

David S.

[peebee]

In:

/root/spot/.config/chromium

or alternative path:

/home/spot/.config/chromium

[mikeslr]

G'day,

Updated to this Chromium-72-as-spot from a fine and spotless Chromium 59.

Where is the config data now held for Chromium?

In v59, I had it linked from each Pup's /root/.config/chromium/ to a common directory on my data partition so all Pups have the same profile data etc. for chromium (screenshot shows a Pup's /root/.config/ with many configs (icons with corner arrows) linked back to data partition directories to allow sharing of just one profile for each application between all Pups on the computer).

But not now as I cannot find where this important information is now stored by v72.

Thanks for any help, or should I just stay with v59?

David S.

David,

peebee's post is correct. But you won't be able to easily link it to a common directory on the data partition. Spot is a limited user which does not have permission to access any folders beyond those within the Spot folder itself.

Perhaps there's a way. It would involve creating a common folder with Spot's limited permissions. Perhaps Mike Walsh knows. If I recall correctly, his set-up generally uses folders shared by several puppies. And the way he creates Google-Chrome64 has a Spot folder in /Home to hold the application itself; but uploads and downloads are managed thru a /root/Spot folder.

[Mike Walsh]

@ David/Mike:-

Mike's got the right of it. I do share many common items between Pups; you, David, were the instigator of all that!

Browser config data, where they run-as-spot, will be found in /root/spot/.config. In the case of these, my remote data partition has a /root/spot directory, which has restricted 'spot:spot' permissions on it. When sharing configs between multiple Pups from here, I sym-link it to the /roof/spot/.config directory. BUT....

Remember one thing. In the process of moving things around in Pup's file-system, you invariably put any 'spot:spot' permissions back to 'root:root' again. So, before you fire the browser up, you'll need to run

Code: Select all

 chown -R spot:spot /root/spot

....which just makes sure you've reset the correct permissions for the spot directory (and contents).

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

This running the browser as 'spot' doesn't seem to be a hard & fast thing amongst the various Chromium-based browsers. Chromium itself, and SRWare's 'Iron' browser - which both Mike and I are very happy with - will both run in either mode (root or spot). Chrome, however, and SlimJet both stamp their feet and throw tantrums if you don't run 'em as a restricted 'user'.....in both cases, refusing point-blank to even condescend to run until you've set them up in the manner they demand. Like a spoilt toddler!

(With SlimJet, you can place the main directory itself in a 'root-controlled' location....but you must 'run' it as 'spot'. Chrome goes one step further; the whole kit & caboodle must be run from a restricted directory; Google are of the firm opinion that this makes you safer browsing the big, bad 'net. )

Gets very confusing, I tell you....

It's obviously some 'flag' or 'switch' or other that determines this behaviour.....except, unlike the majority of the vast number of --switches that are available to the user with these browsers, this particular one has been 'hard-coded' in at the source level. Which indicates a conscious decision by the developer (in this case, Google and FlashPeak) to force their users to run the browser in the way that they wish them to. Because it's not hard-coded at the original source level from the Chromium Project itself.....

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

The other thing to remember is that with the Chromium 'clones', you can share configuration between browsers of a different vintage only so long as they're no more than perhaps 2 or at most 3 build releases apart. If you go any further than this, you'll find that the older versions will throw an error message about the data/settings being from too new a version....

They're quite 'fussy'..!


Mike.

[rufwoof]

Remember one thing. In the process of moving things around in Pup's file-system, you invariably put any 'spot:spot' permissions back to 'root:root' again. So, before you fire the browser up, you'll need to run

Code: Select all

 chown -R spot:spot /root/spot

I believe that in some puppy's if a run-as-spot browser 'auto-updates' that also can reset it to be running as root instead of spot.

You could set spot to be comparable to root if you want to run the browser as 'root'. Me, I go the other way and assign spot its own bespoke shell (simple script that loops around prompting for a command and a case statement that only accepts/runs a very limited number of commands), and just launch the browser using a su to spot action within its own separate environment ('container').

Another factor to consider is that puppy's tend to have spot set up so weakly that elevating to root from spot is trivial. As good a pointless IMO (even if you boot 'clean' after a penetration, that doesn't avoid having someone else having secured your private keys/passwords (access to other sites/servers) and/or got access to your router to redirect its dns or whatever, and/or having inserted a sub-system layer into the boot process).

Yet another way is to run as root, but with root capabilities having been lowered, perhaps to the extent of being comparable to or even lower than a restricted userid, but that is still considered as being userid 'root'

[davids45]

G'day,

Thanks for the replies to my query about where Chromium-72 is hiding its profile/config details.

I briefly tried a few things suggested but these just reminded me of Windows and 'big' Linuxes in introducing complexity and annoyances to a single-user computer.
So I've deleted chromium-72-spotty and its configs and stayed with Chromium-59-spotless.

Fortunately for me, the recently updated iron is still this-user-friendly, the 72 version seems to be running as I like. So there is still a couple of likeable and linkable browsers.

Sorry for wasting your time(s).

David S.

[peebee]

peebee's post is correct. But you won't be able to easily link it to a common directory on the data partition.

It is pretty easy - you just have to change the ownership of the chromium config directory and all its contents to spot:spot ...... root can of course still access such files

[peebee]

For 32-bit LxPupSc and ScPup only ......... a Debian Sid build ............

has a bug:
https://bugs.debian.org/cgi-bin/bugrepo ... bug=927913

[peebee]

Debian chromium_74 crashes when receiving a url request from another application........use with caution!

[peebee]

32-bit:
chromium_74.0.3729.108+pepper_32.0.0.192_lx_spot.sfs

64-bit:
chromium64_74.0.3729.108+pepper_32.0.0.192_lx_spot

n.b. BionicPup64-8.0 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)

[medhor]

I'm a puppy newbie, having some problem to run the leates version:

64-bit:
chromium64_73.0.3683.103+pepper_32.0.0.171_lx_spot

On bionic puppy v 8.0 64-bit

It's don't start.

After digging around I modify the file /usr/bin/chromium-browser

replacing

Code: Select all

run-as-spot /usr/lib64/chromium/chromium --ppapi-flash-path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=${flashver} --disk-cache-size=10000000 --media-cache-size=10000000 --allow-outdated-plugins "$@"

with

Code: Select all

run-as-spot /initrd/pup_ro3/usr/lib64/chromium/chromium --ppapi-flash-path=/usr/lib64/chromium/PepperFlash/libpepflashplayer.so --ppapi-flash-version=${flashver} --disk-cache-size=10000000 --media-cache-size=10000000 --allow-outdated-plugins "$@"

Its working now.

It is the right fix ?
What went wrong?


Thanks

[peebee]

Sorry....

BionicPup64-8.0 requires the 64-bit .sfs to be converted - see: http://murga-linux.com/puppy/viewtopic. ... 205#867205 (use option 2)

New version - 74.0.3729.108

[peebee]

For 32-bit LxPupSc and ScPup only..........

Arch32 build..........

chromium_74.0.3729.169-2.0+pepper_32.0.0.192_lxsc_spot.sfs