keyring backend
- Problem: keyring password prompt in console, in every client run
- Note: in the first run, it asks to create a password for the keyring, also in console.
Also we may take a look to the backend selection because in windows there is no prompt.
h3. Debug
2013-05-20 16:05:58,725 - leap.services.eip.providerbootstrapper - DEBUG - Emitting check_api_certificate {'passed': True, 'error': ''} 2013-05-20 16:06:42,738 - leap.crypto.srpregister - DEBUG - Post to uri: https://api.dev.bitmask.net:4430/1/users 2013-05-20 16:06:42,739 - leap.crypto.srpregister - DEBUG - Will try to register user = ivan 2013-05-20 16:06:42,739 - leap.crypto.srpregister - DEBUG - user_data => {'user[password_salt]': '2cc3b2c4', 'user[password_verifier]': '75dd5e32f11a fe1e5321b35a0445de2cbeeb75701da527e3e3f0e454669c395f93e9385cdf3c254075c7d4d4098d13b8dfe153d4355f7f7915adf7d25ec722eef383a5286f6cb2292bda3bc05d7b095a5 bd82915422aa1bdee202c30129601deac273c9a647dc1b425886a17dd08fd89306a4a400a395bafadd35d2e4afbb013', 'user[login]': 'ivan'} 2013-05-20 16:06:42,740 - leap.config.providerconfig - DEBUG - Going to verify SSL against /home/ivan/.config/leap/providers/dev.bitmask.net/keys/ca/ cacert.pem Please set a password for your new keyring: Please confirm the password: 2013-05-20 16:07:35,420 - leap.services.eip.providerbootstrapper - DEBUG - Checking name resolution for dev.bitmask.net 2013-05-20 16:07:35,440 - leap.services.eip.providerbootstrapper - DEBUG - Emitting name_resolution {'passed': True, 'error': ''} 2013-05-20 16:07:35,441 - leap.services.eip.providerbootstrapper - DEBUG - Checking https for dev.bitmask.net 2013-05-20 16:07:36,803 - leap.services.eip.providerbootstrapper - DEBUG - Emitting https_connection {'passed': True, 'error': ''} 2013-05-20 16:07:36,804 - leap.services.eip.providerbootstrapper - DEBUG - Downloading provider info for dev.bitmask.net
Quoting "python-keyring":https://pypi.python.org/pypi/keyring#configure-your-keyring-lib: ??The python keyring lib contains implementations for several backends, including OSX Keychain, Gnome Keyring, KDE Kwallet and etc. The lib will automatically choose the keyring that is most suitable for your current environment. You can also specify the keyring you like to be used in the config file or by calling the set_keyring() function.??
We may need to make sure that the right backend is choosen every time.
(from redmine: created on 2013-05-21, closed on 2013-07-05, relates #2640 (closed), relates #2960 (closed))