--WHz+neNWvhIGAO8A
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Sep 03, 2003 at 07:15:16PM +0200, Tim Jansen wrote:
> But if I understand it correctly now, it asks for a password at each star=
tup?=20
> That also sounds quite annoying and certainly not what the majority of us=
ers=20
> want.

Well, considering it's a kded load-on-demand module, I assume you'll
actually need it on start-up because it won't start unless an application
demands it. Of course, if applications like Kopete are loaded within a
session, that more or less makes it a permanent module anyway.

Different security levels of wallets would make so much sense. Giving Kopete
access to a MSN account should probably not use the same wallet as loading
my creditcard details for a payment form. In fact, the latter should
probably use a one-time authorization, I wouldn't even want Konq to load my
creditcard details a hour n+1 just because I have used the app to order
something at hour n.

Unless such real-life concerns are addressed properly, KWallet integration
probably will only create huge security risk within KDE instead of securing
data.

(forgive if this is all addressed, but KDE is not in a state where I can
properly experiment with KWallet.. will cvs up again tonight)

Rob
--=20
Rob Kaper     | "They that can give up essential liberty to obtain a little
cap@capsi.com | temporary safety deserve neither liberty nor safety."
www.capsi.com | - Benjamin Franklin, Historical Review of Pennsylvania, 1759

--WHz+neNWvhIGAO8A
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQE/ViNytppIl2G1SjcRAhr5AJ9/vb/IEjDxEcbLk3OEP6HpNoO+jQCbBqpt
cZjdgIEXr2Ln+4tD4Jxndts=
=K1Gj
-----END PGP SIGNATURE-----

--WHz+neNWvhIGAO8A--