Skip to content

Comment on My practical approach to surfing the web safely

Comments

I have a handy little script called `chrome-new` which I use whenever I want to browse one of those few sites that struggles with Firefox. It just starts a clean Chromium with a throw-away profile, then deletes it when I close the browser.

    #!/bin/sh
    TMPDIR=$(mktemp -d /dev/shm/chrome-XXXXX)
    chromium --user-data-dir=$TMPDIR --no-first-run --no-default-browser-check --disable-features=DefaultBrowserPrompt "$@"
    rm -rf $TMPDIR

Is there an advantage over just --guest?

Not sure - I have never used that flag! I like the idea of managing the profile dir myself, because then I know nothing will leak. For example, HSTS state persists across incognito, allowing fingerprinting. I don't know if --guest handles that differently (probably?) but this way, I can be sure.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.