[Solved] Chrome 83.0.4103.61 detected as insecure
-
By the way: Google Chrome should be marked as Insecure by default, becuse it steals your data!
:devil: -
@OLLI_S So why do you use it? There are so many alternatives.
-
I don't use Chrome (I am using Microsoft Edge Chromioum).
The portable version of Google Chrome I have just for VulnDetect! -
-
@Tom : Same problem with Edge chromium today: .44 available at this time and .45 known to be the latest version.
-
@OLLI_S : Agree.
I used to find forbidden Chrome installations by taking them sending data to forbidden anonymizers.
So I do not use it but have to look at it. -
@GregAlexandre said in Chrome 83.0.4103.61 detected as insecure:
@Tom : Same problem with Edge chromium today: .44 available at this time and .45 known to be the latest version.
Edge was updated right now to Version 83.0.478.45
-
@GregAlexandre Where do you download it from?
Whenever we recommend new versions of Chrome, Edge and most other software, then we either already see users running the new version, or we see that the vendor update the versions on their download / release notes / announcements pages.
Only rarely do we see a delay in the exe file being published, mostly it is smaller projects, where they rely on free CDNs or download sites to distribute their software, in these cases we sometimes have to try more than one site, to find one with an updated installer.
-
@OLLI_S : yes. Has to wait less than one hour after my last post to have it updated.
-
@Tom :
- https://www.google.com/chrome/ with "Français - France" as language choice.
- auto-update feature
Both gave the same result: outdated version.
For Edge I only tried thru parameters / about .
I am not surprised but this behavior where updates arrive with some delays in Europe.
My main point was to let you know, if needed, as this can be surprising when displayed in red.
-
@GregAlexandre It is good to know.
The thing is, that we have a bunch of test machines where we apply updates, and as I explained earlier, our packages download the installer from the vendors official sites / CDNs.
Coincidentally, we have some 15 (virtual) test hosts located in France, and I have never noticed such a delay for Chrome (or other software). We deploy updates to at least half of them within minutes after we prep the package and the remainder within a few days.
But I guess you are right, I'm just surprised we don't see it when we test - due to the way we do it, it would cause a 24 hour delay before we reattempt.
-
@Tom : Localization by internet tools is a very funny thing. Some years ago I was able to cross the Atlantic in a second
.
Are you sure that your french hosts are not found in USA or elsewhere? -
-
OK, then I mark this issue as solved.
