From kde-core-devel  Sun Mar 22 12:32:45 2009
From: Dario Freddi <drf54321 () gmail ! com>
Date: Sun, 22 Mar 2009 12:32:45 +0000
To: kde-core-devel
Subject: Root privileges in systemsettings
Message-Id: <200903221332.50939.drf54321 () gmail ! com>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=123772511208881
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1391311.s6JLmz1eGo"

--nextPart1391311.s6JLmz1eGo
Content-Type: Text/Plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello people,

As you might know, I'm in the process of making systemsettings+kcmshell abl=
e=20
to use policykit for getting root privileges and bring back the almighty=20
"Administrator button" (or better not, since it will be thrown away in any=
=20
case).

Though, we have a small problem here regarding multiplatform stuff. PolicyK=
it=20
is strictly for Linux (afaik it doesn't even run on Mac OS), so adding bare=
=20
PolicyKit support would lead to a lot of ifdefs, hence a real mess.

I wrote a mail to kde-windows and kde-mac, but got no replies, so I decided=
 to=20
go on with my idea and propose it here.

What I basically thought about is a library with a Solid-like design for=20
managing authorizations. Then we can create various backends for it (one us=
ing=20
PolicyKit, one using Mac stuff, etc) and abstract the problem by making all=
=20
applications in KDE needing PolicyKit using this new library instead.

A possible take would be reimplementing this in Solid. I know, Solid is=20
hardware specific, but since the design is almost the same, a lot of code=20
would be duplicated.

If you think this is a good idea, I can step forward and provide an API dra=
ft=20
in a while.

Cheers

=2D-=20
=2D------------------

Dario Freddi
KDE Developer
GPG Key Signature: 511A9A3B


--nextPart1391311.s6JLmz1eGo
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEABECAAYFAknGL+4ACgkQaqeZcVEamjubWwCfaBdyEV0fpB1lBMxhcGxnlJGR
QbYAn0JMKQ4re6Siq5SZHDRzSPNsw+m9
=2hPb
-----END PGP SIGNATURE-----

--nextPart1391311.s6JLmz1eGo--