Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Fri 21 Sep 2018, 04:23
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Browsers and Internet
Google Chrome 64-bit SFS packages (with new, default GUI)
Post new topic   Reply to topic View previous topic :: View next topic
Page 16 of 16 [228 Posts]   Goto page: Previous 1, 2, 3, ..., 14, 15, 16
Author Message

Joined: 24 Feb 2014
Posts: 2538

PostPosted: Sun 29 Jul 2018, 17:15    Post subject:  

Mike Walsh wrote:
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).
 Filesize   54.48 KB
 Viewed   193 Time(s)


( ͡° ͜ʖ ͡°) :wq
Back to top
View user's profile Send private message 
Mike Walsh

Joined: 28 Jun 2014
Posts: 4143
Location: King's Lynn, UK.

PostPosted: Tue 07 Aug 2018, 20:32    Post subject:  

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:-


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. Wink

MY PUPPY PACKAGES | 'Thanks' are always appreciated!

Back to top
View user's profile Send private message Visit poster's website 
Mike Walsh

Joined: 28 Jun 2014
Posts: 4143
Location: King's Lynn, UK.

PostPosted: Wed 05 Sep 2018, 06:06    Post subject:  

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

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. Wink

MY PUPPY PACKAGES | 'Thanks' are always appreciated!

Back to top
View user's profile Send private message Visit poster's website 
Display posts from previous:   Sort by:   
Page 16 of 16 [228 Posts]   Goto page: Previous 1, 2, 3, ..., 14, 15, 16
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » Browsers and Internet
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum

Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1494s ][ Queries: 12 (0.0500s) ][ GZIP on ]