Package Details: google-chrome 129.0.6668.58-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only, click to copy)
Package Base: google-chrome
Description: The popular web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 2237
Popularity: 8.05
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-09-17 21:41 (UTC)

Dependencies (12)

Sources (3)

Pinned Comments

gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (UTC) by gromit)

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Stable updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-stable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

Latest Comments

« First ‹ Previous 1 .. 87 88 89 90 91 92 93 94 95 96 97 .. 157 Next › Last »

Det commented on 2015-02-07 16:36 (UTC)

@weirddan455, that's assuming, of course, that you'd be able to break into two distinct places. The only practical way to do Google is to be walking into the server room, hogging a few, and coming up with a great excuse. @ilpianista, are you using Manjaro, or did you touch the line below "Symlinking missing Udev lib..."?

ilpianista commented on 2015-02-07 16:26 (UTC)

/opt/google/chrome/chrome: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory

weirddan455 commented on 2015-02-07 14:28 (UTC)

Any checksum, no matter the algorithm, won't protect you from someone malicously altering the file. Reason being is that if someone manages to replace the file you're downloading it probably wouldn't be too hard for them to simply replace the checksum as well to match the malicous file. The only thing the checksum is good for the way we use it here is to protect against accidental data corruption during the download. MD5 will work just fine for that. Hell even CRC would probably do the job. If you want real data integrety protection, we really PGP signatures. Sadly I don't think Google signs their Chrome DEBs though.

Det commented on 2015-02-07 05:38 (UTC)

We can learn something new every day, but now that the aftermath of my controversial and time-consuming edit[1] for our awesome Wiki admin, Kynikos, has been settled[2], I've now explained the differences between collision and preimage vulnerabilities in MD5, SHA-1 and SHA-2 in the PKGBUILD article: https://wiki.archlinux.org/index.php/PKGBUILD#Integrity_variables This took quite a bit of researching, but it basically means that having MD5 checksums for file integrity are actually fine for now. You don't want to use it for SSL certificates, but carrying out a successful preimage attack requires, even in theory, approximately 2^123.4 ≈ 1.4 × 10^37 operations, which is completely impractical. [1] = https://wiki.archlinux.org/index.php?title=PKGBUILD&diff=359592&oldid=359584 [2] = https://wiki.archlinux.org/index.php/Talk:PKGBUILD#pkgdir

tormund commented on 2015-02-06 18:10 (UTC)

Latest release won't let you press enter to search terms in the omnibox, but it will let you go to suggested websites.

Det commented on 2015-02-05 17:25 (UTC)

You need to press "Flag package out-of-date" from the right :).

Xiaoming94 commented on 2015-02-05 17:23 (UTC)

plz update this package

Det commented on 2015-02-05 10:11 (UTC)

With this specific package it doesn't really make much of a difference (I'd like to see anybody breaking Google's servers), but I could actually convert all of my packages to SHA-256. There's barely any performance impact: $ time md5sum google-chrome-stable_current_amd64.deb | tail -1 md5sum google-chrome-stable_current_amd64.deb 0.11s user 0.01s system 105% cpu 0.118 total $ time sha256sum google-chrome-stable_current_amd64.deb | tail -1 sha256sum google-chrome-stable_current_amd64.deb 0.27s user 0.03s system 96% cpu 0.308 total The poor algorithm has indeed been tortured ever since 2004 (https://en.wikipedia.org/wiki/MD5), and there's no real reason to still be using it. Everybody's just too lazy to do anything about it. Even the Wiki still mentions md5sums: https://wiki.archlinux.org/index.php/PKGBUILD

vikstrous commented on 2015-02-05 06:16 (UTC)

Please use something better than md5, like sha256.

« First ‹ Previous 1 .. 87 88 89 90 91 92 93 94 95 96 97 .. 157 Next › Last »