As discussed in the previous post go to Chrome OS wiki and Welcome to fun with chrome flags. Many of the Chrome users might not aware of the capability of the chrome flags. Before explaining the individual flags we’re gonna discuss this experimental features which might crash or break the browser after changing some settings. With these flags, the user can control the advance privacy and security related features like WebRTC leaks, cached password generation, auto clearing browser data, certificate management and many other networks and hardware related things. First open up the chrome browser and type chrome://chrome-urls to get the list of all available inbuilt flags, around 72 to 75 depends on the version of the browser. Let’s look at some useful flags.
One of the most important chrome://flags I’ve used during the penetration test of the website. with this flag, the user can see the each request browser has performed.
This chrome://flags detects the port activity from starting up to turning off of the device with the timestamp and its user whether it is a portable hard drive, USB, Storage Device, Bluetooth peripherals etc. If the user has inserted the USB then it’ll log its ‘Vendor name’, ‘product name’,’serial number’,’adapter’.
It’ll log the system type (platform) device have connected to if it’s a host OS or virtual machine OS. The user can select the option to show different logs like events device has performed, debug information, operation errors, file information of the successful information, will catch login operations if it is protected with password or encryption. The image on the right will give a better idea.
This chrome://flags will show the DNS queries the particular website has performed with page load counts and other external sites from which the resources are coming from CDNs, Comment systems, Webserver information, third party websites of digital marketing.
This chrome://flags will dump the current state of the browser with Boolean values like enabled and disabled extensions, plugins and other chrome labs experimental features.
The image on right is the snipe of state which shows the stat of the password manager and all plugins that is in use, adobe plugins, Facebook video calling plugin and it shows the permission of the each plugins like ‘Authorization required’ in the video call plugin and other info.
One of the most important chrome://flags to get the network information of the browser. Several options are available like HSTS protocol test, web socket testing, events of hardware to network operations like disks, sockets, UDPs etc.
Event tab logs the UDP requests, API connect jobs, which data is stored on disk cache or socket pool. Socket tab logs idle and active web socket handshakes requested to particular web socket server during the opening of the site. HSTS tab allows you to input, delete and query a domain which you want to get preloaded or not. You can get other information in proxy, cache and timeline tab as per your need.
These chrome://flags are useful for fuzzing of websockets, Setting up HSTS protocol for certain domains, getting the timeline of all the operations.
All of the above i’ve found useful as per the type of need or while collecting the browser artifacts to create the report. These flags can be used for different purposes but mostly it is helpful in digital forensics. Other flags will be discussed here in depth soon. Fore more information on chrome flags go to this blog , Thank you.