Summary: | KDE Wallet is pushy | ||
---|---|---|---|
Product: | [Applications] kwalletmanager | Reporter: | stefano.d |
Component: | general | Assignee: | Valentin Rusu <valir> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | isa-lie |
Priority: | NOR | ||
Version: | 16.08 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
stefano.d
2016-10-30 14:59:18 UTC
Sorry, I can't edit my report. "Know, I service called kded5 " should be "Now, a service called kded5 ...". - You can create a wallet with an empty password. But then the wallet file is not encrypted. - You can use kwallet-pam extension to automatically use the user password to unlock/decrypt the wallet file. You might need to ask in a forum of your distribution to set it up. - for network passwords, you can configure connections to work system-wide, but then the netword password might be stored unencrypted. Actually I reported this, because I wanted a good default behaviour. I want to install Linux for my girlfriend on her PC and I don't want to tell her, that she has to spend hours to configure her PC until it works how she expects it. So, if this is really the solution, I will recommend her Gnome. The default behavior favors security over simplicity, in other words, you need to supply a password to unlock/decrypt the content stored in the wallet. If your distribution does not setup kwallet-pam extension by default, you could search for a distribution that does. This is not something that can be decided by KDE developers. Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |