Bug 92826 - Security Levels per Entry for KWallet
Summary: Security Levels per Entry for KWallet
Status: RESOLVED INTENTIONAL
Alias: None
Product: kwalletmanager
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: George Staikos
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-06 23:02 UTC by Jorge Adriano
Modified: 2004-11-06 23:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jorge Adriano 2004-11-06 23:02:52 UTC
Version:           1.0 (using KDE 3.3.1, SuSE)
Compiler:          gcc version 3.3 20030226 (prerelease) (SuSE Linux)
OS:                Linux (i686) release 2.4.20-4GB

Well some passwords are just more important. There is a lot of debate about Password-less Kwallet, this would easily solve the problem. Here is the general idea:

1. Multiple security levels (Green, Yellow, Red).

2. Each entry is assigned a security level. Default Yellow. When adding an entry you can choose the wallet and the security level (default yellow).

2.1. You can change default security levels per wallet.

3. To access an entry with Level L, Kwallet in mode >= L. (e.g, to access Yellow entries, you need to be in yellow or red mode.)

4. Green mode needs no password. Yellow standard password. Red pass-sentence.

5. higher security levels auto-close with different parameters. So it could go from Red to Yellow alone and eventually to Green on its own.

6. KWallet is on KDE startup with green level.



That's it!! Security and usability! :)
Comment 1 George Staikos 2004-11-06 23:08:39 UTC
Nice idea, but no.

(in any case, wallets have 1 encryption over the whole thing, not per-item.)
Comment 2 Jorge Adriano 2004-11-06 23:16:24 UTC
That was fast! :)

Why can't a wallet be composed of 3 separate parts then, each one with a different encryption though? Compatability with current wallets could be done by assuming yellow level.
Comment 3 George Staikos 2004-11-06 23:21:58 UTC
On Saturday 06 November 2004 17:16, Jorge Adriano wrote:
> ------- That was fast! :)
>
> Why can't a wallet be composed of 3 separate parts then, each one with a
> different encryption though? Compatability with current wallets could be
> done by assuming yellow level.

  Because that's overcomplicated.  Users have the option of an unencrypted 
wallet now, and that's sufficient I think.
 
  Plus management of "security levels" is even more complicated than anything 
we had or have now.  Assuming that entries from various apps are of various 
security levels is quite wrong.  (I have web apps that have much more 
important security levels than local passwords, for instance.)

Comment 4 Jorge Adriano 2004-11-06 23:50:23 UTC
"Because that's overcomplicated.  Users have the option of an unencrypted 
wallet now, and that's sufficient I think."

Yeap I know. 

"Plus management of "security levels" is even more complicated than anything 
we had or have now."  

If a users just accepted the default settings then:
One default wallet, with yellow as default, would be exactly what we had. 
Two wallets, one green the other yellow is exactly what we have now.

"Assuming that entries from various apps are of various 
security levels is quite wrong.  (I have web apps that have much more 
important security levels than local passwords, for instance.)"

Agree... but I never suggested that (?).

I may be missing something...