I would have thought you'd have some respect for how it is not a good idea to circumvent the likes of VLC and Chrome so that they can be run as root when they have been specifically designed to avoid being run as root for security reasons. Increasingly however its become evident that you and other Puppiest have no regard for such security matters.
TBH, Ruffers, it shows you haven't been paying attention as of late. If you had, you would have seen that we've had no choice but to run Chrome et al as a 'normal' user (in this case, spot) for the last 4 or 5 releases. Google simply won't permit it any other way now.....not if you want to maintain sandboxing, and the other built-in security protocols.. And even I'm not daft enough to use the
.....'switch' in the wrapper script any longer. After all, it's slightly crazy not to take advantage of the multiple security protocols available to the browser.....especially when they're provided free of charge, along with the browser itself. The current Chromium-based offerings are very much a 'team effort', with contributions from several individuals over the last year or two.....to enable their use with Puppy, at the same time as running them in the secure manner in which they were intended to be run.
And then there's the business of the downloads. Peebee (who, as you know, packages Chromium for Puppy) and I have taken somewhat different routes over this. Peebee has packaged Chromium to download stuff as 'spot'.....but then immediately makes it available to the entire system by transferring it straightaway to the main Downloads folder with root:root permissions. I had a wee think about this, and came to the conclusion that the decision over whether to leave the download as is with normal 'user' (spot) permissions, or to transfer it to the main Downloads directory and give it root:root permissions should be left to the individual.
So; my current Chrome and Iron packages include a couple of small scripts that place a large green 'tick' in the notification area. If you want to transfer your downloaded item to the main Downloads directory (and make it available to the rest of the system), then you just click on the green checkmark.....and it moves it across and changes permissions for you.
To me, one of the great things about Linux in general (and Puppy in particular) is the matter of maximum choice in all things. It's not my place to hold the hand of other Puppians, to mollycoddle them, and to make their choices for them.....but as a responsible 'packager', to me those choices should be made available to the end user, along with clear definitions as to what is and isn't considered safe. The decision is then down to the individual; remember, one of Puppy's main 'selling-points' over the years has been that the user is in total control of their entire system.
Puppy does move with the times, as you're aware yourself from your experiments with BK's new EasyOS, where everything runs in sandboxed containers. I think even you grudgingly admit that it's somewhat more secure like that.....and who knows, it may even turn out to be the direction Puppy itself follows in years to come.
T'internet landscape is vastly different from what it was nearly 15 years ago, when Puppy first appeared on the scene.....
Edited by Mike_Walsh, 19 May 2018 - 07:02 PM.
Distros:- Multiple 'Puppies'..... and Anti-X 16.1
My Puppy BLOG ~~~ My Puppy PACKAGES
Compaq Presario SR1916UK; Athlon64 X2 3800+, 3 GB RAM, WD 500GB Caviar 'Blue', 32GB Kingspec PATA SSD, 3 TB Seagate 'Expansion' external HDD, ATI Radeon Xpress 200 graphics, Dell 15.1" pNp monitor (1024 x 768), TP-Link PCI-e USB 3.0 card, Logitech c920 HD Pro webcam, self-powered 7-port USB 2.0 hub
Dell Inspiron 1100; 2.6 GHz 400FSB P4, 1.5 GB RAM, 64GB KingSpec IDE SSD, Intel 'Extreme' graphics, 1 TB Seagate 'Expansion' external HDD, M$ HD-3000 'Lifecam'.