Chrome Nags

From iMacros
Jump to: navigation, search

Where does Google Chrome store passwords

Google uses SQLite as the storage mechanism for passwords and other web page related data.

The saved password data is stored in an SQLite database located here:

<UserName>\AppData\Local\Google\Chrome\User Data\Default\Login Data

To perform the encryption (on Windows), Chrome uses a Windows API function which makes the encrypted data only decipherable by the Windows user account used to encrypt the password. So essentially, your master password is your Windows account password. As a result, you get the same kind of security as if you would store all passwords in a plain text file and protect this file with the Windows Encrypted File System (EFS).

How to use separate cookies in incognito mode?

Currently, Chrome creates a fresh, empty cookie jar when "New Incognito Window" is invoked. This cookie jar is shared among all incognito windows and tabs, and will only be destroyed when the last incognito window/tab is closed. In constrast, IE and Firefox do not share cookies between there private sessions.

Solution: Create different user profiles for each instance, this keeps the cookies separated.

How to enable iMacros for Chrome for different user profiles

  1. Use the instructions below to create the profile.
  2. Make sure the iMacros add-on is installed in each profile.
  3. In order to launch Chrome with a different user profile via the iMacros scripting interface (e.g. iimOpen("-cr -crUserDataDir C:\MyProfile")) or with iimRunner (e.g. iimOpen("-cr -runner -crUserDataDir C:\MyProfile")), you need to allow access to file URLs:
    1. Go to Tools - Extensions and click the small triangle next to the iMacros add-on
    2. Make sure "Allow access to file URLs" is checked
Allow access to file URLs (with border).png

How to create different user profiles

What most people want to do is create shortcuts for each Chrome profile they want to use. So that when activated, Chrome brings-up a new window for a specific profile. To do this:

Copy & paste the Chrome shortcut on your desktop, right-click it, go to Properties, and make it look something like this:

'"" --user-data-dir="C:\Location\Of\User\Profile"'

And Chrome will either create or use a pre-existing profile that is there, depending on if it exists or not. Of course, you can choose any location you like. Chrome also creates the folder if it does not exist!

You need to install iMacros for Chrome and any other extension again in each profile that you create. Alternatively you can also copy the content of the profile folder.

How NOT to create different user profiles for use with iMacros

Do not use the "Add new user..." button in the Chrome Settings, use the method specified above.

Do not confuse the "right" option above with the "udd" option described below, which we do not recommend. The "udd" option is Windows-specific and thus might not be supported in the future:

If you add "--enable-udd-profiles" to the the target field of your chrome shortcut it will enable chrome's built in profile support. Just to clarify your shortcut target (on XP anyway) should look something like:

"C:\Documents and Settings\<user>\Local Settings\Application Data\Google\Chrome\Application\chrome.exe" --enable-udd-profiles


Open Chrome from that very link and type CTRL+M, which opens the window in which you can create a new user.

This creates a shortcut that will take you to your profiled version of Chrome.

Chrome Command Line Switches

Part1 Base, Part2

Google Chrome has a number of command line switches which change the behavior of Chrome, some of these switches can be turned on/off in the regular settings menu such as “dns-prefetch-disable” however others cannot.

To launch and use the switches, you append the switch name when calling Chrome on launch like:

“…..\Application\chrome.exe” –crash-test

Which would obviously execute the crash test function.

Here are some more switches:

allow-all-activex always-enable-dev-tools app assert-test automation-channel channel crash-test debug-children debug-print disable-dev-tools disable-hang-monitor disable-images disable-java disable-javascript disable-logging disable-metrics disable-metrics-reporting disable-plugins disable-popup-blocking disable-prompt-on-repost dns-log-details dns-prefetch-disable dom-automation dump-histograms-on-exit enable-file-cookies enable-logging enable-p13n enable-watchdog first-run gears-in-renderer gears-plugin-path geoid hide-icons homepage import in-process-plugins javascript-debugger-path js-flags lang log-filter-prefix log-level make-default-browser memory-model memory-profile message-loop-histogrammer message-loop-strategy new-http no-events no-sandbox omnibox-popup-count playback-mode plugin plugin-launcher plugin-path plugin-startup-dialog process-per-site process-per-tab proxy-server record-mode remote-shell-port renderer renderer-assert-test renderer-crash-test renderer-path renderer-startup-dialog restore-last-session safe-plugins show-icons silent-dump-on-dcheck single-process start-maximized start-renderers-manually tab-count-to-load-on-session-restore test-sandbox testing-channel testshell-startup-dialog trusted-plugins uninstall upload-file use-lf-heap user-data-dir wait-for-debugger-children

For an up-to-date list please see the URLs above.

See Also

IE Nags, IE9 Nags, Firefox Nags

iMacros for Chrome