I just nstalled Google Chrome to test it. Immediately, it asked to open Kwallet. I allowed it, and then I thought... Yikes! Should I have done that?
Why does Google chrome need to see the contents of Kwallet even before I have visited a web site and while all I am doing is configuring it? Is it looking at other stuff I have stored in my wallet?
On 06/30/2011 11:12 AM, Petrus de Calguarium wrote:
I just nstalled Google Chrome to test it. Immediately, it asked to open Kwallet. I allowed it, and then I thought... Yikes! Should I have done that?
Why does Google chrome need to see the contents of Kwallet even before I have visited a web site and while all I am doing is configuring it? Is it looking at other stuff I have stored in my wallet?
I don't think I would assume it is asking for your password in order to look for anything immediately. It should just as easily be opening it to check that the structure it uses/needs exists and then create it if not.
Are you concerned that Chrome maybe doing something evil?
On Thu, 2011-06-30 at 11:53 +0800, Ed Greshko wrote:
On 06/30/2011 11:12 AM, Petrus de Calguarium wrote:
I just nstalled Google Chrome to test it. Immediately, it asked to open Kwallet. I allowed it, and then I thought... Yikes! Should I have done that?
Why does Google chrome need to see the contents of Kwallet even before I have visited a web site and while all I am doing is configuring it? Is it looking at other stuff I have stored in my wallet?
I don't think I would assume it is asking for your password in order to look for anything immediately. It should just as easily be opening it to check that the structure it uses/needs exists and then create it if not.
Are you concerned that Chrome maybe doing something evil?
$ google-chrome --help
[...]
--password-store=<basic|gnome|kwallet> Set the password store to use. The default is to automatically detect based on the desktop environment. basic selects the built in, unencrypted password store. gnome selects Gnome keyring. kwallet selects (KDE) KWallet. (Note that KWallet may not work reliably outside KDE.)
Maybe the autodetection is buggy. I know that on one installation I get the nagging KDE Wallet window all the time (even when revisiting a page I've been on before in the same session), while on the other I never see it. Both are using KDE.
poc
On Thu June 30 2011, Patrick O'Callaghan wrote:
$ google-chrome --help
[...]
--password-store=<basic|gnome|kwallet> Set the password store to use. The default is to automatically detect based on the desktop environment. basic selects the built in, unencrypted password store. gnome selects Gnome keyring. kwallet selects (KDE) KWallet. (Note that KWallet may not work reliably outside KDE.)
Maybe the autodetection is buggy. I know that on one installation I get the nagging KDE Wallet window all the time (even when revisiting a page I've been on before in the same session), while on the other I never see it. Both are using KDE.
Had a similar problem with Chrome just pop up out of the blue. I changed the web browser in systemsettings from "google chrome" to "google-chrome -- password-store=kwallet" and ran like that for a couple days, then gave up and removed the "--passwordstore=..." bit and voila! I am now no longer propmted for my KWallet password. :D
On Thu, 2011-06-30 at 06:16 -0400, John Aldrich wrote:
On Thu June 30 2011, Patrick O'Callaghan wrote:
$ google-chrome --help
[...]
--password-store=<basic|gnome|kwallet> Set the password store to use. The default is to automatically detect based on the desktop environment. basic selects the built in, unencrypted password store. gnome selects Gnome keyring. kwallet selects (KDE) KWallet. (Note that KWallet may not work reliably outside KDE.)
Maybe the autodetection is buggy. I know that on one installation I get the nagging KDE Wallet window all the time (even when revisiting a page I've been on before in the same session), while on the other I never see it. Both are using KDE.
Had a similar problem with Chrome just pop up out of the blue. I changed the web browser in systemsettings from "google chrome" to "google-chrome -- password-store=kwallet" and ran like that for a couple days, then gave up and removed the "--passwordstore=..." bit and voila! I am now no longer propmted for my KWallet password. :D
Thanks, maybe I'll try that on the one that keeps nagging. From your description, clearly it is buggy.
poc
On Thu June 30 2011, Patrick O'Callaghan wrote:
Had a similar problem with Chrome just pop up out of the blue. I changed the web browser in systemsettings from "google chrome" to "google-chrome -- password-store=kwallet" and ran like that for a couple days, then gave up and removed the "--passwordstore=..." bit and voila! I am now no longer propmted for my KWallet password. :D
Thanks, maybe I'll try that on the one that keeps nagging. From your description, clearly it is buggy.
May also need to go in and turn on/off "sync". I messed with that bit as well. Currently disabled, and I don't recall if it was ENabled or DISabled when I changed that.
On 06/30/2011 07:42 PM, Patrick O'Callaghan wrote:
On Thu, 2011-06-30 at 06:16 -0400, John Aldrich wrote:
On Thu June 30 2011, Patrick O'Callaghan wrote:
$ google-chrome --help
[...]
--password-store=<basic|gnome|kwallet> Set the password store to use. The default is to automatically detect based on the desktop environment. basic selects the built in, unencrypted password store. gnome selects Gnome keyring. kwallet selects (KDE) KWallet. (Note that KWallet may not work reliably outside KDE.)
Maybe the autodetection is buggy. I know that on one installation I get the nagging KDE Wallet window all the time (even when revisiting a page I've been on before in the same session), while on the other I never see it. Both are using KDE.
Had a similar problem with Chrome just pop up out of the blue. I changed the web browser in systemsettings from "google chrome" to "google-chrome -- password-store=kwallet" and ran like that for a couple days, then gave up and removed the "--passwordstore=..." bit and voila! I am now no longer propmted for my KWallet password. :D
Thanks, maybe I'll try that on the one that keeps nagging. From your description, clearly it is buggy.
Since I am the only one using this system, I just changed the kwallet settings. I unchecked "Close when unused for XXXX" and checked "Close when last application stops using it".
I get one prompt the first time any application uses the wallet and never get prompted again unless I logout.
Ed Greshko wrote:
Are you concerned that Chrome maybe doing something evil?
Yes. even though I do use google services, I don't trust them and I have never trusted their browser or their addon toolbar, etc. I use firefox and like it, but I wanted to have a look at chrome, because of its recent rise in popularity.
On 06/30/2011 01:14 PM, Petrus de Calguarium wrote:
Ed Greshko wrote:
Are you concerned that Chrome maybe doing something evil?
Yes. even though I do use google services, I don't trust them and I have never trusted their browser or their addon toolbar, etc. I use firefox and like it, but I wanted to have a look at chrome, because of its recent rise in popularity.
I see.... Well, if your level of trust is that low you may be better served by running it on a clean, minimal VM instead of on your "production" system.
Isn't Chrome source code available? I thought it was.
Ed Greshko wrote:
Isn't Chrome source code available? I thought it was.
That doesn't help me a lot.
I took 2 years of Computer Science back in the early 80s (learned pascal, c, assembly language, fortran) and I can still understand short pieces of code, but when it gets complicated or much longer than this post, I am lost. And I certainly do not have the time to examine the code of chrome. I believe it was 28 MB in size.
-
Ed Greshko -
John Aldrich -
Patrick O'Callaghan -
Peter G.