31

I suggest to store a few additional things for each entry in KWallet:
- time of creation
- time of last acccess
- total number of accesses
The goal is to allow users to decide which entries in KWallet to keep, which to remove. Over time (years) KWallet gets poluted by hundreds of stale entries. For example because of pim migration efforts (!) or simply web sites not visited any more. Currently it is not that easy to say which entries are still required. Especially for things like mail accounts that carry cryptic names best you can do is guess.
The additional information would simplify that task without being difficult to implement.

With KDE-4.8 to be release end of the month it looks as if the aged KWallet is finally to be replaced by the Secret Service. So most likely no one wants to invest time into KWallet from now on.
I did not yet have time to take a look at the Secret Service, but maybe someone who did can answer these questions:

- is the issue I addressed solved in Secret Service ?
- or do we have the same problem over again ?

Thanks !

SecretService doesn't really make a difference.

Basically in short it used to go:

KDE App -> KWallet
and
Gnome App -> Gnome Keyring

Now, with secret service it goes

KDE App -> Secret Service -> API KWallet/Gnome Keyring
Gnome App -> Secret Service -> API KWallet/Gnome Keyring

So everyone shares keyring, but the remaining backends are still in existance. Anyway, that's now all a bit OT.

Another thought:
writing a wallet entry on each access is required to store the time of last access and to count the number of accesses of a single entry. This obviously has a penalty in efficiency. So it might make sense to offer if such data should be recorded. An additional configuration flag could control this during the wallet setup.