Google Chrome 64-bit packages - [CLOSED]

[rufwoof]

From version 66 onward, Google started becoming really strict about security.

Thanks Mike. As a long term ff-esr user I've transitioned over to iridium in recent weeks and love it. Running under OpenBSD - its Pledged (so additional checks to trash out anything that looks suspect). In Oct/Nov when OBSD 6.4 is released unveil will also be available in stable (veils the complete filesystem and then selectively unveils what is permissible). Iridium is like chromium, but with even more controls over phoning home. Works really well with googledocs. Primarily it is my dektop now (using cwm, so generally you launch things via the exec key and type the first 2 or 3 letters of the program you want to run and press enter). Hope the bookmarks bar remains, as that is in effect my launcher. I also have a local html/javascript file to show the date and time in the tab title (I add my bookmarks to the content of that web page). behind that, the desktop, just a picture.

For data isolation I login at the console and run tmux and mc in one of those windows. Nice and colourful and enables scrolling etc. So fundamentally running all internet facing as userid user, all data stored under root (I further store data files in a encrypted file filesystem)

I do notice that periodically google trashes a aw-snap message apparently as it detects dubious web page content. However the more google tightens up on general browser and browsing security the better IMO. Its great for viewing pdf's, watching videos, etc. I even have a local html/javascript file for a calculator that meets my needs. Pretty much base OpenBSD + iridium + mc ... is my full desktop installation although I do have a few other small programs installed on top of that such as ddclient that provides static domain name to dynamic IP redirection i.e. to my OpenBSD httpd server (base OBSD comes with httpd, mail server, X ...etc all included, and all with sensible secure defaults so pretty much minimal configuration required).

[Mike Walsh]

Evening, all.

Further to the inclusion of the 'Spot2Root' utility in these Puppy Chrome packages, I've since realised that the problem exists in the other direction too.

Most of the time, I'm in one or the other of my many 32-bit Pups. I've primarily used my original Tahrpup64 install for building these 64-bit browser packages, and for experimenting with the increasing numbers of AppImages that are becoming available.....almost all of which are being built as 64-bit only.

It's only since installing Xenialpup64 7.5 last week that I've begun to spend more time in a 64-bit Pup, and used my own Chrome & Iron browser packages for any length of time.

I came up with the 'Spot2Root' utility for the simple reason that, with these browser packages now running as spot all the time (since that's the only way they will now run in Puppy), I was starting to come up against the problem that downloads naturally had spot:spot permissions. Which played havoc, especially with any packages/executables you might download; they needed permissions changing in order to work correctly with Pup's root:root model.

Thus the 'Spot2Root' utility was born, and has for the last few releases been built-in to the browser package itself.

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

I only occasionally upload; mostly when I release new packages, and need to upload them to one or the other of my file-hosting accounts. This last few days, I've realised that unless you change permissions to 'spot:spot' first, Chrome and Iron will turn their noses up at them, and won't upload them. They go through the motions.....but nothing actually happens.

Accordingly, I've re-written the 'Spot2Root' utility. It adds a new 'Uploads' directory to /root/spot, and now includes an additional script which changes permissions for the contents of that directory in the other direction, from the normal 'root:root' to 'spot:spot'. The whole thing is still controlled from the notification area, but instead of the pre-existing green 'check mark' I've been using up until now, it's now a two-way up/down arrow icon instead. Like this:-





Clicking on the icon now brings up a new GUI:-





.....which gives the option of changing file permissions in either direction. For downloads, it'll run the existing 'spot-to-root' script in /usr/local/bin, and output your downloaded files to your normal Downloads directory with 'root:root' permissions.

For uploads, you move/copy your files into /root/spot/Uploads, ready to upload them, then click the icon, and click the 'uploads' button. This just chowns permissions to 'spot:spot', prior to actually uploading them.

(I know this all seems a bit involved, but this GUI stuff is for newcomers to Puppy.....many of whom have, of course, been used to GUIs in Windows, and in many cases are completely lost with the terminal. For the rest of us, who know what we're doing, it's probably quicker to just chown through the terminal as normal.)

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

This modified utility will be built-in to the next Puppy Chrome package in its entirety when Chrome 69 is released sometime next month. For now, I'm providing a .pet package which adds the extra functionality to the existing browser packages, which can be found here:-

http://www.mediafire.com/file/fodthu8c5 ... 1.pet/file

Also included is the freshly-recompiled 64-bit current version of YAD (0.40), which powers the GUIs.....and which is required by one or two of the very recent YAD features I've made use of. The 'pinstall.sh' script removes the now-redundant ~/my-applications/bin/S2R.sh and /usr/local/lib/X11/mini-icons/green-tick.png, prior to installation of the new items.

Here's hoping some of you may actually find this new stuff useful. I'd like to be able to set things up eventually so that as you 'drop' files into ~/spot/Uploads it'll automatically swap permissions without additional mouse-clicking.....but, for now, that's a wee bit above my pay-grade. So until then, this will have to do.


Mike.

[Mike Walsh]

Afternoon, all.

The current stable version of Chrome - Google_Chrome-69.0.3497.81-amd64 - is now available for download, from the new location referenced in post #1.

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

Well, here it is, boys & girls. The fully-modernized, bang up-to-date, 10th anniversary release of Google Chrome!





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

Changes and updates in this release are as explained here, on the regular Chrome blog page.

40 security issues have been addressed since the previous release.

The biggest issue of note with this release hits you in the face as soon as Chrome fires up; the new-look to the GUI. Google have been tweaking things in the background for the last few months, and at long last the sloped tabs have bitten the dust. In come tabs very reminiscent of the older 'Australis' Firefox interface; more space between your extensions, your bookmarks; a softer, 'rounder' look to the omnibox.

This is now the default appearance. If you want to change back to the older 'look', simply modify my instructions from the previous post.

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

I explained in a previous post about the need to 'set-up' the now-included glib-schemas so that downloading/uploading will work without crashing the browser, by running

Code: Select all

glib-compile-schemas /usr/share/glib-2.0/schemas

There is no need to manually run this command any longer. A small script has been placed in /usr/sbin & sym-linked into /root/Startup, which will automatically run the compile command at boot time.

The 'Spot2Root' file permissions changer has been updated, too. It now works with uploads as well as downloads.....as explained in the previous post.

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

Credits go to:-

Battleshooter - for help with the self-contained NSS libs'n'stuff several releases back.
belham2 - for cobbling together the 'launch' script that is now employed.
And further back, 01Micko (the 'head honcho'), and iguleder - both of whom have indirectly helped keep this thread going for as long as it has, with references & links.

Thanks must also go to OscarTalks and peebee, for suggestions and assistance over the last couple of years.

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

Any problems, drop me a line. You know where to find me.

Have fun.


Mike.

[Mike Walsh]

Evening, all.

Just to let y'all know, there's been a change in packaging 'strategy'.

Following the revelation by Mikeslr on the Bionicpup64 thread that the 'standard' package with Chrome running-as-spot from /root/spot now refuses to 'play ball', I've adopted the method as practised by FatDog for some time now.

Henceforth, Chrome will now be situated in /home/spot (still running as user 'spot', though). This brings it more into line with Google's preferred standard Linux practice (which is employed by just about every major distro), of running the browser from the /home/*user directory*.

You'll also notice that there is now a single, 'generic' package for all Pups that can run it. Testing has shown that there is no longer any need for 'buntu- and Slacko-specific variants; this single package now works equally well for all.

The SFS package is available as usual. For the first time, I'm also providing Chrome as a .pet package.....mainly for anyone who runs a 'full' install (including certain of Barry's 'Quirky' creations, which are apparently designed to run this way.) As most of you are aware, full installs cannot make use of the SFS package's advantages, namely that of loading/unloading 'on-the-fly', and thereby not permanently occupying 'Puppy-space' in the save-file/folder. They don't have the SFS loading mechanism, so anything installed using an SFS is there permanently, with no way to remove it except by doing it all manually. SFS packages don't have the 'petspecs' file within them, so the PPM has no information to work with.

So; one single SFS, and one single .pet. Makes life easier all round for everybody.....especially me! Downloads available from the usual location referenced at the beginning of this thread.

Have fun. Any probs, you know where to find me.


Mike.

[mikeslr]

As you may already know I was rather peeved by having to adjust to the changes Google-chrome & company have forced us Puppy Users to make. Unlike most (almost all) other Linux Distros, Puppies maintain a firm distinction between what constitutes storage and RAM. Primarily, Puppies work in RAM, reading files into it as and when they are needed. It's one of the reasons Puppies can perform as fast as they do, and RAM being cleared on shutdown/reboot provides a level of security other distros --which treat RAM and Storage as a unified system, constantly writing to storage-- can't provide.

But with its unified system mind-set, Google has now made it necessary to run Chrome-and-clones as a limited user, and that requires that these applications under Puppies, their configuration files and bookmarks, and the files you download using them or will upload using them all reside in the limited User Spot [or its equivalent] and while there possess the permissions allowed that limited User. Under Puppies, all files in the folder Spot occupy RAM, and this is the case whether Spot is located in /root or its own folder /home/spot.

Thoughtfully, Mike Walsh has built into his construction of Google-Chrome a module for quickly getting files you've downloaded and files you intend to upload into and out of the Spot folder, and changing their permissions from those of root to spot for uploads and from that of spot to root for downloads. The module places a launcher on the taskbar which expedites these procedures.

Still, getting files into and out of RAM would be a chore if some Puppy devotee hadn't established other tools.

The upload tool merely changes permissions but presumes that the file is already in .../spot/Uploads. To quickly get a file (or folder) into /spot/Uploads you can Right-Click the file/folder wherever it happens to be and select "Copy to". Thanks to whoever created that module among its attributes are not only the facility to copy files/folders from their current location to another, but to "bookmark" that other location so it can again be quickly chosen later. So /spot/Uploads was bookmarked in that tool. It was also bookmarked in rox. Once google-chrome has uploaded the file/folder to the Web, I can quickly open rox to /spot/Uploads and delete the file/folder --freeing up RAM for actual work.

Use of the spot-to-root module actually requires little forethought. You've already downloaded the file or files and it/they is/are located in .../spot/Downloads. The module moves such files out of /spot/Downloads to /usr/share/Spot2Root* where permissions are changed, and then moves them to /root/Downloads. Most Puppies will already have that folder --if it doesn't already exist firefox and clones will create it. And most Puppy users will be content with that. But I run Puppies with AutoSave Removed and try to avoid executing a Save without having a good reason. /root/Downloads is in RAM and rebooting/shutting down without Saving will clear RAM, obliterating its contents. Which meant I had to take the time to move files from /root/Downloads to somewhere they will continue to exist after a reboot/shutdown.

So what I did was modify Mike Walsh's yad command. You'll find this command at /usr/local/bin with the name spot-to-root. Opened in geany, there's a line which reads:

mv -v /usr/share/Spot2Root/* ~/Downloads/"#1CHROME_Downloads"

or something like that without the "bolding". [I edited it before writing this, and that version existed before his build with spot in the home folder].

At any rate, my edit of that line now reads:

mv -v /usr/share/Spot2Root/* /mnt/home/my-stuff/Downloads/

So, after files are moved out of .../home/spot, and had their permissions changed while in /usr/share/Spot2Root/ they are moved to a folder on /mnt/home: out of RAM, and written to Storage for later use.

You may want to change the above line to one more appropriate to your system. My 64-bit Puppies share a partition with one of the "regular" Linux Distros. As there are folders on that partition relating to that Distro, a "my-stuff" folder reduces confusion.

* For the security conscious, /usr/share/Spot2Root is a folder not "on the path"; hence not where your operating expects to find executables for how little time they may reside there. Neither by the way is anything on /mnt/home.

[Mike Walsh]

Morning, Mike.

Yeah, sorry about that "~/Downloads/*1-Chrome_Downloads" thing. That was an oversight on my part, and left over from the module as it works for my own system.

All my major directories in /root are sym-linked to large, external data drive partitions anyway. I have a lot of stuff in /Downloads, much of which I like to leave where it is, subject to a periodic 'spring-clean'. Creating the "*1-Chrome_downloads" sub-directory simply makes it easier to locate new stuff immediately!

You know as well as I do, Mike, that with the huge variety of different hardware Puppians run, along with personal preferences as to how things are done, means that there cannot be a universal 'one-size-fits-all' solution. Naturally, a degree of editing is required, but at least it's simple enough to do, so.....thanks for posting this, and for clarifying a few points for the benefit of all.

Cheers, mate.


Mike.

[sheldonisaac]

The current stable version of Chrome - Google_Chrome-69.0.3497.81-amd64 - is now available for download, from the new location referenced in post #1.

Mike, I just noticed this Sept 5 post, and downloaded that Chrome.

But now I'm confused about these: can someone clarify (my brain is old and foggy)?

-rw-r--r-- 1 root root 71720960 Sep 20 08:16 Google_Chrome-69.0.3497.81-amd64-bionic.sfs
-rw-r--r-- 1 root root 84951040 Sep 25 09:37 Google_Chrome-69.0.3497.81-amd64.sfs

[Mike Walsh]

@ sheldon:-

Hm. What's the problem?

As far as the older version goes, it runs fine in Tahrpup64, the 64-bit Slackos and Xenialpup64. It won't behave itself with Bionicpup64, however.....as mikeslr found out.

The 'generic' version I uploaded last night is the new version, which now runs from /home/spot, rather than /root/spot.

This is the version which will be in use going forward, since it appears to behave itself in all 64-bit Puppies.

Is the fog 'thinning-out' at all?


Mike.

[sheldonisaac]

@ sheldon: The 'generic' version I uploaded last night is the new version, which now runs from /home/spot, rather than /root/spot.

This is the version which will be in use going forward, since it appears to behave itself in all 64-bit Puppies.

Is the fog 'thinning-out' at all?

Yes, Mike.

Thank you,
Sheldon

[Mike Walsh]

@ sheldon: The 'generic' version I uploaded last night is the new version, which now runs from /home/spot, rather than /root/spot.

This is the version which will be in use going forward, since it appears to behave itself in all 64-bit Puppies.

Is the fog 'thinning-out' at all?

Yes, Mike.

Thank you,
Sheldon

No worries. You're welcome..!


Mike.

[Mike Walsh]

Evening, boys & girls.

The current stable version of Chrome - Google_Chrome-70.03538.67-amd64 - is now available for download, from the location referenced in post #1.

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

This is the release which prompted some discussion about whether the Forum would still be accessible in Chrome.....partially over-hyped by yours truly, who got ever so slightly hold of the wrong end of the stick.!

http://www.murga-linux.com/puppy/viewtopic.php?t=114452

Apologies for being 'alarmist' over that.....but some of that has been reported in previous release posts on this thread anyway. Since I'm posting from Chrome 70 right now, I think we can safely discount that (despite there being a big, bright red 'Not Secure' now displayed on the left of the address bar when typing in the editor.) It still works (for now, at least!).....which is the main thing.


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

Changes and updates in this release are as explained here, on the regular Chrome blog page.

23 security issues have been addressed since the previous release.

Once again, the new GUI is very much noticeable. Google have been tweaking things in the background for several months now, and at long last the sloped tabs have bitten the dust. In come larger tabs very reminiscent of the older 'Australis' Firefox interface; more space between your extensions, your bookmarks; a softer, 'rounder' look to the omnibox.

This is now the default appearance. If you want to change back to the older 'look', simply modify my instructions from an earlier post.

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

One other issue of note, and one which will be of interest to the security/privacy-conscious amongst you.....and that is the business of Chrome automatically signing you in, and 'syncing', the moment you sign in to any Google apps; the Drive, Google Docs, etc, etc. This was introduced in the last release, Chrome 69, and immediately created uproar.

Google have apparently backed down from this move following all the hoo-ha they inadvertently caused with it. There is now an 'option', buried away in the 'Settings' page, to control this. Go into the 'Advanced section', and, fairly near the top, you'll find a slider switch to 'Allow Chrome sign-in'. You'll need to de-activate this; Google are still hoping you won't find it, and it's opt-out, rather than opt-in.....
----------------------------------------------------

There is no need to manually run the

Code: Select all

glib-compile-schemas /usr/share/glib-2.0/schemas

..command any longer. A small script has been placed in /usr/sbin & sym-linked into /root/Startup, which will automatically run the compile command at boot time.

The 'Spot2Root' file permissions changer has been updated, too. It now works with uploads as well as downloads.....as explained in an earlier post. Following an exchange of ideas & points raised via PM with mikeslr, I've added an extra line to the 'spot-to-root' module of the Permissions Changer which sits in the task-bar; when you select 'Spot-to-Root (for downloads)' in the GUI, ROX (or whatever your default file-manager happens to be) will now open on your 'Downloads' directory, ready to retrieve the newly-downloaded item.

Just cuts down on the need for a few additional clicks, since most of us usually wish to access downloaded items straight away...

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

Credits:-

Battleshooter - for help with the self-contained NSS libs'n'stuff several releases back.
belham2 - for cobbling together the 'launch' script that is now employed.
And further back, 01Micko (the 'head honcho'), and iguleder - both of whom have indirectly helped keep this thread going for as long as it has, with references & links.

Thanks must also go to OscarTalks and peebee, for suggestions and assistance over the last couple of years.

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

Any 'issues', give me a shout. We should be able to sort 'em out.

Enjoy!


Mike.

[sheldonisaac]

The current stable version of Chrome - Google_Chrome-70.03538.67-amd64 - is now available for download, from the location referenced in post #1.

Got it, many thanks. Posting from it now, under bionicpup64 7.9.5.

(despite there being a big, bright red 'Not Secure' now displayed on the left of the address bar when typing in the editor.

Oh, now I see it.

It still works (for now, at least!).....which is the main thing.

Yep.

Thanks again,
Sheldon

[rufwoof]

Chrome 70 (Fatdog version anyway), shows some lines in the location indicators in the vertical side slider bar when you do a find/search. Not noticed that before, if a new feature - I like it.

[Mike Walsh]

Hi, ruffers.

Can't say as I've noticed it myself, but then my Pups are all 'pure' Puppy. Perhaps peculiar to FatDog, as you say.....maybe even peculiar to your monitor? Don't know about that one...


Mike.

[step]

It's a Chromium feature. I run Opera, which is Chromium based, and I can see the search location lines in the scroll bar.

[Mike Walsh]

It's a Chromium feature. I run Opera, which is Chromium based, and I can see the search location lines in the scroll bar.

Mm. Well, even Chrome itself is just another Chromium-based browser.....but Big Brother must have suppressed those in the released Chrome code, 'cos there's absolutely no sign of 'em for me.


Mike.

[rufwoof]

I wonder if it could be the choice of theme being used. I've Morpheon Dark installed (one of the best dark themes around IMO, handles shading of active/inactive tabs very well).

OT: Wishing you mother well Mike. Mine's a couple of years older and been through similar lately.

[Mike Walsh]

Thanks, ruffers. Much appreciated.

As the old saw goes, you only get one Mum.....so it's in our own best interests to look after 'em!

She's not out of the woods yet, though I believe she's over the worst of it. Everything takes longer to clear up, the older you get.....a fact I'm steadily discovering for myself.....!

She's had her own routine for getting over illnesses, etc, for decades; she retreats to her 'nest', keeps herself warm (and well-hydrated).....and usually, Mother Nature takes care of the rest.

I just wish more folks would take that attitude. It's really not very clever, struggling on (especially when you're infectious), and infecting everyone you encounter, left, right & centre. I wish somebody had told the bloody woman who gave it to her at the opticians a fortnight ago; she was hacking, coughing, spluttering, and just literally sneezing all over everybody else in the waiting-room. Not even the decency to cover her mouth with a hanky.....or even her hand!

I'm waiting (with bated breath) to see whether I come down with it myself.....


Mike.

[rufwoof]

I just wish more folks would take that attitude. It's really not very clever, struggling on (especially when you're infectious), and infecting everyone you encounter, left, right & centre. I wish somebody had told the bloody woman who gave it to her at the opticians a fortnight ago; she was hacking, coughing, spluttering, and just literally sneezing all over everybody else in the waiting-room. Not even the decency to cover her mouth with a hanky.....or even her hand!

Sounds like you need to be more assertive Mike. But respect that's not in your nature. Personally I'd have had my mum out of there like a shot letting everyone know the reason why in the process. Post mid 80's you do have to fight ever harder as more often otherwise others just wont care. Xmas eve 2 years ago we had to ambulance mum/nan into hospital and a few days later due to antibiotic overload (medics trying to find the right one) she ended up with C-Diff and had to be isolated for around 3 weeks. Pretty much daily battles with staff (in particular consultants) and without those battles she'd have been dead and buried shortly after. As is, despite greater frailty, we still have the blessing of her presence (and continual criticisms primarily directed at her only child/son - just take it on the chin and consider that her frustrations have to be vented somewhere otherwise that in itself can cause medical issues. Fortunately we don't live together, around 200m apart but dine etc. together, and she leads a reasonably independent lifestyle where she feels comfortable and in control - that also helps maintain my own sanity).

[Mike Walsh]

Evening, kiddiwinks.

The current stable version of Chrome - Google_Chrome-71.0.3578.80-amd64 - is now available for download, from the location referenced in post #1.

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

Nothing especially new to report; with this release, Google have finally completed the whole 'https is normal/http isn't' thing (at long last). Now, https sites have no prefix to the address at all; http sites have 'Not secure' tacked in front, with the legend in red lettering on any page where you might give out potentially sensitive information.....like this very one I'm composing my post on.

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

Changes and updates in this release are as explained here, on the regular Chrome blog page. (I'm a week late with this one, but real life gets in the way.)

43 security issues have been addressed since the previous release.

Once again, the new GUI is very much noticeable. Google have been tweaking things in the background for the better part of the last year, and the iconic sloped tabs have finally bitten the dust. In come larger tabs very reminiscent of the older 'Australis' Firefox interface; more space between your extensions, your bookmarks; a softer, 'rounder' look to the omnibox.

This is now the default appearance. If you want to change back to the older 'look', you can reverse my instructions from an earlier post.

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

One other issue of note, and one which will be of interest to the security/privacy-conscious amongst you.....and that is the business of Chrome automatically signing you in, and 'syncing', the moment you sign in to any Google apps; the Drive, Google Docs, etc, etc. This was introduced in the Chrome 69 release, and immediately created uproar.

Google have apparently backed down from this move following all the hoo-ha they inadvertently caused with it. There is now an 'option', buried away in the 'Settings' page, to control this. Go into the 'Advanced section', and, fairly near the top, you'll find a slider switch to 'Allow Chrome sign-in'. You'll need to de-activate this; Google are still hoping you won't find it, and it's opt-out, rather than opt-in.....
----------------------------------------------------

There is no need to manually run the

Code: Select all

glib-compile-schemas /usr/share/glib-2.0/schemas

..command any longer. A small script, which has been placed in /usr/sbin & sym-linked into /root/Startup, now automatically runs the compile command at boot time.

The 'Spot2Root' file permissions changer has also been updated. It now works with uploads as well as downloads.....as explained in an earlier post. Following an exchange of ideas & points raised via PM with mikeslr, I've added an extra line to the 'spot-to-root' module of the Permissions Changer which sits in the task-bar; when you select 'Spot-to-Root (for downloads)' in the GUI, ROX (or whatever your default file-manager happens to be) will now open on your 'Downloads' directory, ready to retrieve the newly-downloaded item.

Just cuts down on the need for a few additional clicks, since most of us usually want to access downloaded items straight away...

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

Credits:-

Battleshooter - for help with the self-contained NSS libs'n'stuff several releases back.
belham2 - for cobbling together the 'launch' script that is now employed.
And further back, 01Micko (the 'head honcho'), and iguleder - both of whom have indirectly helped keep this thread going for as long as it has, with references & links.

Thanks must also go to OscarTalks and peebee, for suggestions and assistance over the last couple of years.

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

Any problems, ya know where to find me.

Enjoy!


Mike.