diff options
| author | erg@google.com <erg@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-02 18:39:22 +0000 |
|---|---|---|
| committer | erg@google.com <erg@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-03-02 18:39:22 +0000 |
| commit | d0aff40acbcf6714daef11e343f409bb11ea7678 (patch) | |
| tree | df07343e1a7cc0cf50d23e84896a080103065bfc /content | |
| parent | fc0f7aa679b48f458ecf4e207eefbceef429f063 (diff) | |
| download | chromium_src-d0aff40acbcf6714daef11e343f409bb11ea7678.zip chromium_src-d0aff40acbcf6714daef11e343f409bb11ea7678.tar.gz chromium_src-d0aff40acbcf6714daef11e343f409bb11ea7678.tar.bz2 | |
GTK: Refuse to run as root.
Running chrome with sudo will change the owner of chrome's config files. This
is really bad and more people accidentally run 'sudo chrome' once and then
screw their profile up.
Inspired by a real life support case this morning and rereading jwz's take on
the issue on evanm@'s blog.
BUG=74594
TEST='sudo chrome' pops up a nice error message and all the files in the profile directory aren't owned by root.
Review URL: http://codereview.chromium.org/6591083
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@76565 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content')
0 files changed, 0 insertions, 0 deletions