bitmask_client.git/src/leap/crypto, branch release-0.2.0 [bitmask_client] make file_path explicit 2012-10-10T18:56:46+00:00 kali kali@leap.se 2012-10-10T18:56:46+00:00 dd446094737ec8274f8c5c3d59ab1466e2ebacc0 






pep8
2012-10-05T16:51:51+00:00

kali
kali@leap.se

2012-10-05T16:51:51+00:00

0576427f697fa631d8f5cc2fc596c60bce38dda3












use keyring to store user password
2012-10-05T00:30:50+00:00

kali
kali@leap.se

2012-10-05T00:30:50+00:00

7c659fed65f08f2b52f0320c99a456679749e3f3

using a quite lame cryptedfile by the moment until dbus bug
makes gnome-keyring usable again or we come up with the
encrypted database solution. we might want to explore the
option of using this python-keyring with the different
native backends for win and macosx.

for now: we generate a random secret that we store in the qsettings file.
so, the whole thing is just to avoid plaintext stuff.
for this, we could have done rot13, haha.





using a quite lame cryptedfile by the moment until dbus bug
makes gnome-keyring usable again or we come up with the
encrypted database solution. we might want to explore the
option of using this python-keyring with the different
native backends for win and macosx.

for now: we generate a random secret that we store in the qsettings file.
so, the whole thing is just to avoid plaintext stuff.
for this, we could have done rot13, haha.