1,368 karma · joined July 9, 2013
Docker isn't the disease, its use in such manner is just a symptom.
https://nakedsecurity.sophos.com/2020/01/20/facebook-and-ins...
$ help set
...
-e Exit immediately if a command exits with a non-zero status.
-E If set, the ERR trap is inherited by shell functions.
-u Treat unset variables as an error when substituting.
-o option-name
Set the variable corresponding to option-name:
pipefail the return value of a pipeline is the status of
the last command to exit with a non-zero status,
or zero if no command exited with a non-zero status[1] https://weblogs.asp.net/soever/returning-an-exit-code-from-a...
[2] https://octopus.com/blog/powershell-exit-codes
[3] https://community.idera.com/database-tools/powershell/powert...
If you want to see what it does:
mkdir junk
cd junk
wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
ar x google-chrome-stable_current_amd64.deb
tar xf data.tar.xz
cat opt/google/chrome/cron/google-chrome
It's not nefarious - it's well-documented and explained.It's just making a decision for me that, as an administrator, I need to be the one deciding instead.
> What’s the smallest, hardest to notice malicious change I can make in the supply chain of software development to enact the most disruptive change?
* Critical projects may have very little activity/maintenance. For example, Bash 4.0 to Bash 5.0 was only 123 commits over 8 years. But, Bash is a absolutely a critical project (ask any org about how much work they had to do when affected by https://en.wikipedia.org/wiki/Shellshock_(software_bug) ).
* A measure of criticality should understand _as many of the various forms of dependence on software_ that may occur that it can. Dependencies can take many forms, such as:
a package manager resolving a dependency
a user purchasing a mobile phone with software pre-installed
a user visiting a website (react/jquery/etc)
etc.
* Criticality should understand if, how, and when dependencies are updated. For example, fixing a bug in Chrome and distributing that fix to 80% of users in 1 week is feasible. Fixing a bug in Bash and distributing that fix to 80% of users in 1 week is not so feasible.
But, I also don't see anyone ever talk about this, and I think it's worth people being aware.
If I fork one of the aforementioned Chromium packages, is my fork covered under that agreement? Is my right to build and produce my own binaries from the original unmodified source still intact?
* Alpine Linux (community port) - https://git.alpinelinux.org/aports/tree/community/chromium/A...
* Arch Linux (svntogit, AUR) - https://github.com/archlinux/svntogit-packages/blob/1e8f3fe7... - https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=chrom...
* Fedora Linux - https://src.fedoraproject.org/rpms/chromium/blob/e78656ce58d...
* Gentoo - https://github.com/gentoo/gentoo/blob/9acf51b665b6f4b5b97edb...
* OpenSuSE - https://build.opensuse.org/package/view_file/openSUSE:Factor...
* Slackware - http://www.slackware.com/~alien/slackbuilds/chromium/build/c...
* Ubuntu, Linux Mint (Canonincal Chromium Snap) - https://git.launchpad.net/~chromium-team/chromium-browser/+g...
[1] https://developers.google.com/terms (specifically: "You will only access (or attempt to access) an API by the means described in the documentation of that API. If Google assigns you developer credentials (e.g. client IDs), you must use them with the applicable APIs. You will not misrepresent or mask either your identity or your API Client's identity when using the APIs or developer accounts." and "Developer credentials (such as passwords, keys, and client IDs) are intended to be used by you and identify your API Client. You will keep your credentials confidential and make reasonable efforts to prevent and discourage other API Clients from using your credentials. Developer credentials may not be embedded in open source projects.")
[2] https://www.chromium.org/developers/how-tos/api-keys (specifically: "Note that the keys you have now acquired are not for distribution purposes and must not be shared with other users.")
If built without API keys, Chromium warns 'Google API keys are missing. Some functionality of Google Chrome will be disabled.' [4] [5]
The APIs used include [6]:
* Calendar API
* Contacts API
* Drive API (Optional)
* Chrome Remote Desktop API
* Chrome Spelling API
* Chrome Suggest API
* Chrome Sync API
* Chrome Translate Element
* Chrome Web Store API
* Chrome OS Hardware ID API (Optional, Chrome OS)
* Device Registration API (Optional, Chrome OS)
* Google Cloud DNS API
* Google Cloud Storage
* Google Cloud Storage JSON API
* Google Maps Geolocation API (Optional)
* Google Maps Time Zone API
* Google Now For Chrome API (Optional)
* Nearby Messages API
* Safe Browsing API
* Speech API
[1] https://git.alpinelinux.org/aports/tree/community/chromium/A...
[2] https://github.com/archlinux/svntogit-packages/blob/packages...
[3] https://git.launchpad.net/~chromium-team/chromium-browser/+g...
[4] https://chromium.googlesource.com/chromium/src/+/9a11dadde80...
[5] https://sources.debian.org/patches/chromium/83.0.4103.116-1~...
[1] https://github.com/flutter/engine/blob/080fbcb1759e5916f0d6c...
Dichotomous was chosen because it was the correct word, not for any other reason.
git config --global help.format man