Philip Martin wrote on Fri, Feb 03, 2012 at 10:02:06 +0000: > Julian Foad <julianf...@btopenworld.com> writes: > > > * Brings kwallet to the same behaviour as Gnome keyring. > > I've realised there is another difference in the current behaviour. The > way auth works is that Subversion records whether a particular provider > was used to store a particular password. The KDE provider will only > prompt to open the wallet when the auth data indicates that KDE was used > to store a particular password. The GNOME provider prompts to unlock the > keyring whenever any password is requested, before checking the auth > data to see if this particular password was stored in the keyring. > > I don't see any advantage to the GNOME behaviour, it looks more like a > bug than a feature.
That behaviour is defensible. "Why should any random app I run know what passwords my keyring stores?" Compare how Subversion does not disclose the names of directories one doesn't have read access to. > > -- > uberSVN: Apache Subversion Made Easy > http://www.uberSVN.com
