All 1,400 Google Chrome CLI flags

Re:All 1,400 Google Chrome CLI flags by Grimburger on Wednesday December 21, 2022 @06:47PM (#34087920)

If you want to stop the inevitable new chrome 0-days:

    --js-flags="--jitless"

Blows my mind you can't turn off JIT in the config. It's a searchable setting in Firefox and on by default in Edge's Super Duper Secure mode.

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by dataflow on Wednesday December 21, 2022 @07:10PM (#34088081)

How do you set that to run on auto-run when the OS starts? Or in general, when Chrome is launched in some other way than you typing that on the command-line?

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by tacotime on Wednesday December 21, 2022 @07:14PM (#34088120)

At least on Windows, you should be able to modify the target property of the program’s shortcut to add any desired flags. Then use that shortcut to launch, or drop it in the startup folder. On Linux idk, maybe an alias?

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by dataflow on Wednesday December 21, 2022 @07:16PM (#34088138)

What shortcut though? Auto-launch is automatically set by Chrome in the registry, and Chrome really doesn't like you to mess with things it manages in general, and would eventually overwrite this in any case. Also I _think_ messing with shortcuts sometimes has weird effects with Chrome, like on taskbar grouping, though it's been a while since I've tried.

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by HideousKojima on Wednesday December 21, 2022 @07:15PM (#34088128)

In Windows, at least, you can make a batch file to launch Chrome with that option, and then use a shortcut to that batch file to open Chrome.

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by OkayPhysicist on Wednesday December 21, 2022 @07:23PM (#34088185)

You can skip the batch file and just include the flag in the shortcut.

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by ravenstine on Wednesday December 21, 2022 @08:02PM (#34088428)

How much of a performance penalty is there for turning off JIT? Are there any other consequences?

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by Operative0198 on Wednesday December 21, 2022 @11:29PM (#34089799)

Encryption libraries such as libsodium no longer work. Some services like protonmail that require to use client device encryption will fail.

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by Dwedit on Wednesday December 21, 2022 @08:16PM (#34088521)

Jitless will not protect you from errors in the DOM implementation that cause use-after-free.

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by sebazzz on Thursday December 22, 2022 @10:49AM (#34094550)

The point of decreasing attack surface is increasing security. While the solution of OP will not prevent the issue you mentioned, it certainly decreases the attack surface.

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by chlorion on Wednesday December 21, 2022 @08:35PM (#34088654)

Could you explain a little bit more in depth on how to do this on firefox?

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by mtmail on Wednesday December 21, 2022 @08:51PM (#34088756)

https://superuser.com/questions/1668807/how-to-disable-jit-c...

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by cpeterso on Wednesday December 21, 2022 @09:00PM (#34088808)

You can turn off the “javascript.options.baselinejit” and “javascript.options.ion” (Ion is the optimizing JIT) preferences in about:config, but you are definitely voiding the warranty and running an untested configuration by doing this!

https://searchfox.org/mozilla-central/rev/57527d50ef5d3df412...

[ Parent | on HN ]

Re:All 1,400 Google Chrome CLI flags by wfh on Wednesday December 21, 2022 @09:22PM (#34088939)

Sure, you can use the enterprise policy:

https://chromeenterprise.google/policies/#DefaultJavaScriptJ...

And this existed before SDSM... in fact SDSM depends on the code landed in Chrome that backs this policy.

[ Parent | on HN ]