Registered Member
|
I'm looking for help clearing up some confusion about how best to deal with the presence of both "old" and "new" Kwallets on the "new" KDE releases distributions are shipping. I know that's happening because all apps have not been yet been ported.
So... 1. On a clean new install, when the dialogue pops up to ask if I want to migrate an old Kwallet, what is the best response? Should I ignore it? Should I cancel it? Should I provide the requested password? If so, *what* password? It apparently wants the password used for the "old" wallet, but, if course, there isn't one. 2. If I respond to the migration dialogue correctly, will all "old" apps automatically use the "old" wallet without further intervention and without pestering me for passwords? 3. Is the "new" wallet structure functional? I.e., is the current release version also functioning without constant user intervention and provision of passwords? If not, what's the best practice for a user when an app wants to use the "new" wallet? 4. If I create a GPG key on a new clean install before the migration dialogue appears, does that impact the response I should give that dialogue? 5. Can I create a GPG key on a new install and expect both old and new wallet frameworks to automatically use it to open their wallets, without intervention by me? |
Registered users: Bing [Bot], Evergrowing, Google [Bot]