I am trying to verify some sites to get ready for the chrome 66 official release.
Reading through the bulletin https://security.googleblog.com/2018/03/distrust-of-symantec-pki-immediate.html it suggests chrome canary would display the page error.
However when I check a known affected site, I only receive the console warning. Is there a flag I need to turn on?
Chrome version: Version 67.0.3364.0 (Official Build) canary (64-bit)
The console warning would be sufficient in most cases, but I need to verify, permanent HTTPS redirects.
Chrome is going to distrust Symantec in 2 steps
In Chrome 66 - SSL/TLS certificate from Symantec that was issued
before June 1, 2016, it will stop functioning in Chrome 66
In Chrome 70 - All remaining Symantec SSL/TLS certificates will stop
working. This cannery is not yet released, planed to release in July 20, 2018
So your certificate may be in the second category. That's why you get only the warning message in console.
Related
For Android Version, less than 11 My app is working fine. But for the versions of Android 11, it shows a message " Please install Chrome Stable 72 or later" when I try to open the app.
Change dependency from
implementation 'com.github.GoogleChrome:custom-tabs-client:a0f7418972'
to
implementation 'com.google.androidbrowserhelper:androidbrowserhelper:2.2.0'
Also make sure Launcher activity in manifest imported from androidbrowserhelper
com.google.androidbrowserhelper.trusted.LauncherActivity
More migration details you can found here
Trusted Web Activity was introduced in Chrome version 72. The issue there is not related to the Android version, but that the version of Chrome installed on the devices showing this message is earlier than 72.
installing the latest version of Chrome from Google Play should solve the issue.
I'm experiencing a bug in GoogleChrome's Trusted Web Activity feature. We've launched a Progressive Web App in the app store using TWA and it runs fine on Android Version 10 (API 29). On other versions of Android it shows a toast message reading "Please install Chrome Stable 72 or later". This occurs on older and new versions of GoogleChrome.
Has anyone experienced this bug before?
When i tried to log a bug report on the Google Chrome's Github they say the best place to ask questions about TWA's is on StackOverflow.
Does anyone know how to disable [violation] in Chrome since recent updates?
I'm currently at Version 71.0.3578.98 (Official Build) (64-bit)
For the record, to save you from telling me to untick the check box or type in -[violation]in "filter" this is what the dev tools look like:
On my local machine i have been using --disable-web-security --user-data-dir
to disable the web security. After upgrading to Chrome Version 66 i have started getting Blocked current origin from receiving cross-site document at ... warning. How to disable the web security for this version of chrome ?
Found a workaround mentioned in https://www.chromium.org/Home/chromium-security/site-isolation
C:\Program Files (x86)\Google\Chrome\Application>chrome.exe --disable-web-securi
ty --user-data-dir --disable-features=CrossSiteDocumentBlockingIfIsolating
This has apparently been fixed in Chrome 67. You can find the bug I reported and a workaround here. The command-line workaround requires you to start Chrome with the following argument:
--disable-features=CrossSiteDocumentBlockingIfIsolating,CrossSiteDocumentBlockingAlways
Simply add
--disable-site-isolation-trials
This works in Chrome 68.
My Chrome automatically updated itself to Version 46.0.2490.71 (64-bit) today 10/14/15, and it looks like the developer tool is broken – it can not be launched.
I uninstalled Chrome latest, and installed Version 45, the developer tool is working fine. But then Chrome immediately upgrades itself to Version 46 again.
I tried to stop the auto upgrade of Chrome by: defaults write com.google.Keystone.Agent checkInterval 0
that does not seem to have any effect – Chrome still tried to auto-upgrade itself.
Is there anyone else using Chrome latest and have the same issue?