On Friday 21 August 2009, Dario Freddi wrote:
> Hello list,
>
> As you might or might not know, GSoC is over, just like my student's
> project. Nicola has worked on a framework to elevate privileges in a
> secure, user friendly way in KDE applications, OS and backend agnostic (it
> uses policykit on linux, to be clear).
>
> Nicola, as part of his project, already ported kcmodule and systemsettings
> to support this new framework, and ported the date/time kcmodule to it. You
> can see everything waiting to be merged in
> branches/work/{kdelibs-kauth,kdebase- kauth}.
>
> Now, we should be all happy to have working kcmodules as root again, and
> this time with a secure and elegant solution, but it doesn't stop here. My
> plan is now to make other pillars of KDE use this framework. In this mail,
> I'm talking about KIO and GHNS.
>
> By now, when KIO, trying to read or write on a file, finds out that it has
> no permission to do so, it simply quits the job. I would like to integrate

I don't understand this sentence:

> KAuth into KIO. In this case, when trying to read a file on which the user
> has no read permission, it would check if the user is authorized to do so,

Authorized to do what ?
Doesn't the "no read permission" mean that the user is not authorized to read 
the file ?

> eventually ask for password, and eventually perform the job.

Which password ?

Alex