Chrome logo

Warnings[edit]

Chrome is non-freedom software!

See Avoid non-freedom software.

Documentation for this is incomplete. Contributions are happily considered! See this for potential alternatives.

Installation[edit]

These instructions are cumbersome due to Google Chrome Repository Insecurity.

(Based on Linux Software Repositories instructions.)

Signing Key Installation[edit]

Digital signatures can increase security but this requires knowledge. Learn more about digital software signature verification.

Download the signing key.

scurl-download https://dl.google.com/linux/linux_signing_key.pub

View OpenPGP key information.

gpg --keyid-format long --import --import-options show-only --with-fingerprint linux_signing_key.pub

pub   dsa1024/A040830F7FAC5991 2007-03-08 [SC]
      Key fingerprint = 4CCA 1EAF 950C EE4A B839  76DC A040 830F 7FAC 5991
uid                            Google, Inc. Linux Package Signing Key <linux-packages-keymaster@google.com>
sub   elg2048/4F30B6B4C07CB649 2007-03-08 [E]

gpg: key 7721F63BD38B4796: 2 signatures not checked due to missing keys
pub   rsa4096/7721F63BD38B4796 2016-04-12 [SC]
      Key fingerprint = EB4C 1BFD 4F04 2F6D DDCC  EC91 7721 F63B D38B 4796
uid                            Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>
sub   rsa4096/78BD65473CB3BD13 2019-07-22 [S] [expires: 2022-07-21]

Convert assci armored linux_signing_key.pub to gpg keyring format linux_signing_key.pub.gpg. ^[1]

gpg --no-default-keyring --keyring linux_signing_key.pub.gpg --import linux_signing_key.pub

^[2]

Create keyring with the RSA 4096 signing key only.

gpg --no-default-keyring --keyring linux_signing_key.pub.gpg --armor --export "EB4C 1BFD 4F04 2F6D DDCC EC91 7721 F63B D38B 4796" | gpg --dearmor --no-options --no-default-keyring > google.gpg

Install the Google RSA 4096 APT signing key.

sudo cp google.gpg /etc/apt/trusted.gpg.d/google.gpg

Avoid Google Chrome Automatic Repository Configuration[edit]

Due to Google Chrome Repository Insecurity.

Create file /etc/default/google-chrome to avoid Google Chrome Automatic Repository Configuration. ^[3]

Note: this will only work if Google Chrome Repository hasn't been previously added.

sudo touch /etc/default/google-chrome

Repository Installation[edit]

Open file /etc/apt/sources.list.d/google-chrome.list in an editor with root rights.

(Kicksecure ™ inside Qubes: In Template)

This box uses sudoedit for better security. This is an example and other tools could also achieve the same goal. If this example does not work for you or if you are not using Kicksecure ™, please refer to this link.

sudoedit /etc/apt/sources.list.d/google-chrome.list

Paste.

deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main

Save.

Package Installation[edit]

Pick a package version.

google-chrome-stable
google-chrome-beta
google-chrome-unstable

Example below installs google-chrome-stable.

Install google-chrome-stable.

1. Update the package lists.

sudo apt update

2. Upgrade the system.

sudo apt full-upgrade

3. Install the google-chrome-stable package.

Using apt command line parameter --no-install-recommends is in most cases optional.

sudo apt install --no-install-recommends google-chrome-stable

The procedure of installing google-chrome-stable is complete.

Related[edit]

Footnotes[edit]

↑ Because in next step, gpg can only work with keyrings. Not with assci armored public key files. This is to import only the newer signing key. Avoiding to import the insecure legacy DSA 1024 signing key.

↑

gpg --no-default-keyring --keyring linux_signing_key.pub.gpg --armor --export "EB4C 1BFD 4F04 2F6D DDCC EC91 7721 F63B D38B 4796" | gpg --import

gpg: key 7721F63BD38B4796: 2 signatures not checked due to missing keys
gpg: key 7721F63BD38B4796: public key "Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: no ultimately trusted keys found

↑
Note: Installing Google Chrome will add the Google repository so your system will automatically keep Google Chrome up to date. If you don’t want Google's repository, do “sudo touch /etc/default/google-chrome” before installing the package.

Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.

Kicksecure ™ ...

Donate

FREE · PLUS · PREMIUM Support

At Kicksecure we believe in freedom and trust. That's why we fully support Open Source and Freedom Software. Learn more.

Kicksecure ™ is supported by Evolution Host DDoS Protected VPS.

Kicksecure ...

The personal opinions of moderators or contributors to the Kicksecure ™ project do not represent the project as a whole. By using this website, you acknowledge you have read, understood, and agree to be bound by these these agreements: Terms of Service , Privacy Policy , Cookie Policy , E-Sign Consent , DMCA , Imprint Kicksecure ™ © ENCRYPTED SUPPORT LP, 2022

Have you found our Documentation, Design and Developer Portal links?

[1] Because in next step, gpg can only work with keyrings. Not with assci armored public key files. This is to import only the newer signing key. Avoiding to import the insecure legacy DSA 1024 signing key.

[2] 
gpg --no-default-keyring --keyring linux_signing_key.pub.gpg --armor --export "EB4C 1BFD 4F04 2F6D DDCC EC91 7721 F63B D38B 4796" | gpg --import

gpg: key 7721F63BD38B4796: 2 signatures not checked due to missing keys gpg: key 7721F63BD38B4796: public key "Google Inc. (Linux Packages Signing Authority) <linux-packages-keymaster@google.com>" imported gpg: Total number processed: 1 gpg: imported: 1 gpg: no ultimately trusted keys found

[3] 
Note: Installing Google Chrome will add the Google repository so your system will automatically keep Google Chrome up to date. If you don’t want Google's repository, do “sudo touch /etc/default/google-chrome” before installing the package.

[1]

[2]

[3]

Chrome

Contents