No, I will not add your apt repo.
It started with Chrome. Google distributes Chrome for Linux via .deb or .rpm.
I won't speak to the RPM, but the .deb is crazy.
If you extract it, you can see:
$ TEMPDIR=$(mktemp -d)
$ dpkg -X ./google-chrome-stable_current_amd64.deb $TEMPDIR
If you look in the extracted files, it includes:
$ ls -al etc/cron.daily/google-chrome
lrwxrwxrwx 1 browser browser 37 Apr 21 10:50 etc/cron.daily/google-chrome -> /opt/google/chrome/cron/google-chrome
$ file opt/google/chrome/cron/google-chrome
opt/google/chrome/cron/google-chrome: POSIX shell script, ASCII text executable
Looking in that script, it adds a keyring in /usr/share/keyrings:
GPG_FILE="/usr/share/keyrings/google-chrome.gpg"
install_key() {
#...
# Use a temporary file to ensure atomic updates
echo "$PGP_KEY_DATA" | base64 -d >"$GPG_FILE.$$.tmp"
chmod 644 "$GPG_FILE.$$.tmp"
mv "$GPG_FILE.$$.tmp" "$GPG_FILE"
}
And adds an apt source signed by that key:
gen_sources_content() {
cat <<EOF
### THIS FILE IS AUTOMATICALLY CONFIGURED ###
# Changes to this file will not be preserved.
# This file will not be recreated if removed.
X-Repolib-Name: Google Chrome
Types: deb
URIs: https://dl.google.com/linux/chrome-stable/deb/
Suites: stable
Components: main
Signed-By: $GPG_FILE
EOF
}
Effectively, this is giving Google root on your system, right?
For Antigravity, they are more direct:
From the download page, it just
prompts you to add the apt repo directly.
For Chrome, I usually install it using the following script: