This post is intended to collect a random set of questions I’ve been asked multiple times about the new Chromium-based Edge. I’ll add to it over time. I wouldn’t call this a FAQ because these questions, while repeated, are not frequently asked.
Can I get a list of all of the command line arguments for Edge?
Unfortunately, we are not today publishing the list of command line arguments, although in principle we could use the same tool Chromium does to parse our source and generate a listing.
In general, our command-line arguments are the same as those in Chrome (Warning: This list may be outdated), with the exception of marketing names (e.g. Chrome uses
--incognito while msedge.exe uses
--inprivate) and restricted words (sometimes Edge replaces
Can I block my employees from accessing the edge://flags page?
You can add “edge://flags” to the URLBlocklist if desired. Generally, we don’t recommend using this policy to block edge://* pages as doing so could have unexpected consequences.
Note that, even if you block access to edge://flags, a user is still able to modify the JSON data storage file backing that page: %LocalAppData%\Microsoft\Edge\User Data\Local State using Notepad or any other text editor.
Similarly, a user might specify command line arguments when launching msedge.exe to change a wide variety of settings.
Can I disable certain ciphers, like 3DES, in the new Edge?
The new Edge does not use SChannel, so none the prior SChannel cipher configuration policies or settings have any effect on the new Edge.
Chromium explicitly made a design/philosophical choice (see this and this) not to support disabling individual cipher suites via policy. Ciphersuites in the new Edge may be disabled using a command-line flag:
msedge.exe –cipher-suite-denylist=0x000a https://ssllabs.com
A few other notes:
- The cipher suite in use is selected by the server from the list offered by the client. So if an organization is worried about ciphers used within their organization, they can simply direct their servers to only negotiate cipher suites acceptable to them.
- The Chrome team has begun experimenting with disabling some weaker/older ciphersuites; see https://crbug.com/658905
- If an Enterprise has configured IE Mode, the IE Mode tab’s HTTPS implementation is still controlled by Internet Explorer / Windows / SChannel policy, not the new Edge Chromium policies.
Can I use TLS/1.3 in the new Edge?
TLS/1.3 is supported natively within the new Chromium-based Edge on all platforms.
Chromium-based Edge does not rely upon OS support for TLS. Windows’ IE 11 and Legacy Edge do not yet support TLS/1.3, but are expected to support TLS/1.3 in a future Windows 10 release.
For the time being, enabling both TLS/1.3 and TLS/1.2 is a best practice for servers.
Can Extensions be installed automatically?
Enterprises can make extension install automatically and prevent disabling them using the ExtensionInstallForcelist Policy. Admins can also install extensions (but allow users to disable them) using the ExtensionSettings policy with the installation_mode set to normal_installed.
Here are the details to install extensions via the Windows Registry. Please note that if you want to install extensions from the Chrome WebStore, then you must provide the Chrome store id and update url: https://clients2.google.com/service/update2/crx.