On Friday 18 February 2011 20:07:36 Patrick O'Callaghan wrote:
> On Fri, 2011-02-18 at 23:45 +0100, Julian Aloofi wrote:
> > Am Freitag, den 18.02.2011, 16:52 -0430 schrieb Patrick O'Callaghan:
> > > When opening a new page, the latest Google Chrome (10.0.648.82 beta,
> > > F14) frequently pops up a KDE Wallet dialogue asking for a keyring
> > > password. This seems unrelated to whether the page itself wants a
> > > password.
> > >
> > > No previous version of Chrome did this, in fact I'm surprised Chrome
> > > has any interaction with KDE at all.
> > >
> > > Has anyone seen this? I'm asking here before reporting to BZ.
> > >
> > > poc
> > Chrom(e/ium) supports native backends for password storage under Linux
> > now, and these include KWallet and the GNOME keyring. I suppose this is
> > completely intentional. See this upstream ticket, looks like they
> > enabled it now: http://code.google.com/p/chromium/issues/detail?id=12351
> > I think there is a --password-store command line flag that determines
> > the backend used by the browser, you might want to look into that if you
> > don't like the idea of storing the passwords in KWallet.
> I don't mind it in principle. What I mind is it trying to access the
> wallet when there is no secure info to be stored in it (these are just
> random pages, not password dialogues), and furthermore not remembering
> the wallet password but repeatedly asking for it.
Yes, I misunderstood your question, sorry about that. For me Chrome is
accessing kwallet without asking for a password. What do you have in KDE
Wallet Configuration -> tab Access Control -> kdewallet -> Chrome as policy?
Mine says "Always Allow".
It has no entry for Chrome, nor does there appear to be any way to add
one. If I can't fix this I'm going to disable Kwallet entirely.