On Wednesday 06 February 2013 14:28:17 Aurélien Gâteau wrote: > On 05.02.2013 21:34, Valentin Rusu wrote: > >> > >> I assumed the "Disconnect" button listed applications authorized to > >> access > >> the wallet. The "Authorized applications" tab was thus another way > >> to show > >> its content. But it seems I got it wrong. What does the "Disconnect" > >> button > >> really list? > > > > kwalletd keeps track of the applications that open wallets. It's dbus > > interface provide a command to selectively disconnect an application > > from it. > > kwalletmanager obtains the list of the applications connected to the > > current > > wallet and build from it the popup menu under the "disconnect" > > button. > > Thanks, I understand it better now. Assuming it was also possible to > get > a list of the authorized applications, I created a new revision of the > mockups which show the list of currently connected applications as well > as the list of authorized applications: > > http://agateau.com/tmp/kwalletmanager/3/ > > I think it is good to create a separate tab for those because this way > the application can provide an explanation of the list(s). Being not > intimate with the way KWalletManager works, I didn't understand what > the > "Disconnect" button would do. This may happen to others as well :) >
Nice proposal. I'll stick with your sketch as it'll provide also for the future, when we'll switch to ksecretsservice. Thanks. > It's worth asking however if users really need a list of the > applications currently accessing the wallet. I have the feeling users > are more concerned about which applications are allowed to read their > wallet than which applications are currently doing so, but maybe I am > missing a situation in which one would want to disconnect applications? Well, it's also about providing application information for hackers. Why hide information if it's freely available? :-) -- Valentin Rusu (vrusu) IRC: valir KSecretsService (aka KSecretService, KWallet replacement)
