summaryrefslogtreecommitdiff
path: root/src/leap/bitmask/util/keyring_helpers.py
AgeCommit message (Collapse)Author
2016-04-07[style] pep8Kali Kaneko
2015-06-22[feat] replace old log handler with new oneIvan Alejandro
Replace logging.getLogger with custom get_logger. Remove some unneeded dependencies and reorder other.
2014-07-31Do not default to SecretService keyringTomás Touceda
2014-07-31Enable keyring againTomás Touceda
2014-07-24Disable user/pass remembering temporarily.Ivan Alejandro
Set the keyring to None in order to simulate an always unavailable keyring, that way we avoid the possibility of the user running into the existing keyring issues. See https://leap.se/code/issues/4190 Update comparisons to do a proper comparison with `None`. Fix login widget 'enabled' changer in order to change the 'remember' widget *only* if we have an usable keyring.
2014-01-17defend against keyring errorsKali Kaneko
on certain settings, like a virtualenv with symlinks, I'm getting errors after a suspend, related to a error to connect to the dbus socket. wrapping all of it in a conditional we avoid that kind of error.
2014-01-11workaround for using keyring inside a virtualenvKali Kaneko
(securestorage backend) This is related to research #4190 and #4083. I didn't resolve them, but I ended understanding a bit more what kind of issues can we be having with those. This workaround is more than anything a cleanup on that for future work, and is making me able to test the client much more nicely inside a virtualenv (where the default keyring selecting was the plaintext one). For this to work inside a virtualenv, one have to install SecureStorage, which in turns depends on python-dbus, which is basically uninstallable using pip inside a venv. So, symlinking to the rescue! it needs gi/repository and pyobject to be symlinked too. but at least you don't have to type the pass every time. I don't know what should be do in the long term with this issue. Some of us were not too fond on using the keyrings at all. We don't have many options among all the keyring backends, and sadly many of them depend on PyCrypto. So probably roll our own backend. Yay.
2013-09-18fix keyring problem with importsKali Kaneko
2013-08-12move everything into bitmask namespaceKali Kaneko