kdeinit - kio - stand alone

[Kevin Krammer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday, 23. September 2002 12:31, Rob wrote:

> My preferred approach would be the other way around, though.
> I'd like to have files kio.allow and kio.deny to allow/disallow apps to
> use kio.
> But that's just my opinion, and I only started thinking about it when
> you mentioned it...

I also like this idea.
I imagine something like they cookie handling in Konqueror.
A newly installed KDE would only allows programs from the oficial KDE 
packages to access remote ioslaves (kio_file would be ok for all IMHO)

If another program request a slave KDE would popup a message similar to 
the Cookie warning:
"Program ... wants to access remote resource ..."
() this time
() always

[allow] [deny]

Cheers,
Kevin

- -- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Kevin Krammer <kevin.krammer at gmx.at>
Developer at the Kmud Project http://www.kmud.de/
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9jvRbnKMhG6pzZJIRAuw5AJ48Rj2fQIqavr7rtM0YtW1S+B1pDgCfTrCm
YbRL2KqbeHSWJV9Jr2iDnUY=
=wdJI
-----END PGP SIGNATURE-----
___________________________________________________
This message is from the kde mailing list.
Account management:  http://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.