All of these, no issue so far. https://malwaretips.com/threads/lis...al-flags-for-google-chrome.41686/#post-707991
Chrome.exe --disable-reading-from-canvas Flags: #enable-future-v8-vm-features #enable-permissions-blacklist #extension-content-verification #reduced-referrer-granularity #enable-site-per-process #disallow-doc-written-script-loads #enable-appcontainer #enable-framebusting-needs-sameorigin-or-usergesture
I published my flags in this thread tho there're some changes from then, and actually that was one of my custom settings for different Chrome profiles. It's sad to see Kees left, but I'd like to ask him if document.write setting actually increase security (I know it can increase performance tho). Tho it's bit OT, These days I think ValidateAdminCodeSignature do not increase actual security so I don't take the fact Chromium being not signed as advantage. This is because most of real EoP techniques couldn't be prevented by that tweak, as it has nothing to do with already running privileged process.
@142395 Most of those type of scripts are injected by third-party ads and analytics. I think a good way to look at it is it can help in all three areas of security, privacy and performance. It certainly cannot hurt.
FWIW ~ I was using Refresh with 67 (chrome://flags/#top-chrome-md) 68 broke Refresh, for me. I have to open new tab to unbreak Refresh.
Got these ones tweaked by me. Question, which of them can be left as default and which are obsolete. Strict site isolation for instance? Isn't this now enabled by default? https://i.imgur.com/PwMvrz3.png
I would leave them that way. If you explicitely set them to disabled/enabled you can make sure that these flags are still disabled/enabled even if Google have decided to change the default.
some of them are used by "default". as mood said - only on demand. lol, this is firefox, cant open flags, wodnering loss of bookmarks^^ b2t Fast tab/window close - default is ENABLED TLS 1.3 is used when asked for. DEFAULT what i have set currently chrome://flags/#account-consistency DISABLED chrome://flags/#smooth-scrolling ENABLED because i had trouble with used extension "SmoothScroll" - no smooth scrolling HTH
Once a feature has finished its experimental stage, that flag disappears from about:flags tho some flags have been there for years. If you want to make sure that a flag is enabled/disabled regardless of its default, then do so and if not sure, do not touch. For other switches I search in this site. Once a switche has become obsolete it's removed from the list.
i dont think so. the sandboxing capabilities of Chrome are linked to the multi-process feature (if im not wrong).
I do know that you can disable it with the "vivaldi.exe --no-sandbox" prefix, but this only works when you launch it via a shortcut. If it's launched via some other app then the sandbox is once again active. BTW, in Firefox 62 it's possible to disable the multiple process feature, it made FF 62 run a bit better with Sandboxie, but didn't solve the freezing problem completely.
Hey! don't say that buddy! In 2019 I'll still need the fabulous Sandboxie! About Chrome blocking code injection I put my hopes in Curt: https://forums.sandboxie.com/phpBB3/viewtopic.php?f=11&t=26095&p=134558#p134558
If that is your purpose, search in the registry with 'chrome.exe" -- "%1"' w/out single quotation. What keys will be found depends on your OS, but for all keys found, change it like this: '...\Google\Chrome\Application\chrome.exe" -- "%1"' to '...\Google\Chrome\Application\chrome.exe" --no-sandbox -- "%1"' Be careful of space. If you use 2+ accounts, repeat it for all accounts you use. No idea about Vivaldi, but maybe you can apply the same, just by substituting chrome.exe by vivaldi.exe.
I've noticed that both Chrome and Vivaldi now run smoothly with Sandboxie even if the Chromium sandbox is enabled, so I have decided not to disable it anymore, but thanks anyway.
