[Ksecretservice-devel] Re: Fwd: Re: Re: ACL handling

Michael Leupold lemma at confuego.org
Mon Oct 11 11:18:25 CEST 2010

Am 10.10.2010 22:53, schrieb Valentin Rusu:
>> Am Mittwoch, 6. Oktober 2010, 20:02:52 schrieb Valentin Rusu:
>>>>> - this behavior should be adjusted by the means of o policy file ;
>>>>> the policy file should be under the responsibility of the client
>>>>> application (e.g. Kontact application should install it's policy file
>>>>> it it wants ACL handling).
>>>> I'm not yet sure what you mean with the policy file. Could you please
>>>> explain a bit more?
>>> Suppose an executable A wants to share it's secrets with another
>>> executable B, but wants to deny sharing with any other executable. In
>>> this case, an external policy file would be required, and this file would
>>> be under the responsibility of executable A developer.
>> Wouldn't it be easier to delegate the decision to the user? From my
>> experience with wishlist items and bug reports power users want things
>> like the ability to choose which collection to store an application's
>> secrets into (maybe the same for all their mail applications or for
>> everything that is about networking). It seems like those features would
>> have to override the default decision taken by the application developer.
> Well, maybe we'll implement ACL handling in several steps, as I understand
> that your KWallet experience gave you a good graps of what users need. Then,
> along the road, if needed, we may offer the policy files I proposed.

Well, I'd rather say a mediocre grasp :) After all once wishes are 
implemented new wishes turn up. A step-by-step implementation sounds 
like a good idea. The policy file sounds more like something to help the 
developer which might be good in the long run.


More information about the Ksecretservice-devel mailing list