bitmask_client.git/src/leap/gui, branch release-0.2.0 [bitmask_client] comment out the set_password call until we fix #744 2012-10-10T22:22:49+00:00 kali kali@leap.se 2012-10-10T22:22:49+00:00 a964b9e55a53b1d87d296e0f3b5295b0366c5967 






add feedback for connection error during signup
2012-10-09T19:34:21+00:00

kali
kali@leap.se

2012-10-09T19:34:21+00:00

5adb36218a96c05034c546c302c1861b4c6e5d46

Closes #724





Closes #724







catch timeout and specify kind of signup error
2012-10-07T20:53:16+00:00

kali
kali@leap.se

2012-10-07T20:53:16+00:00

8a594577660d78a4f0f9d3c5f5902dff3911e010












fix hexlify + add regex validator for usernames
2012-10-07T18:50:07+00:00

kali
kali@leap.se

2012-10-07T18:50:07+00:00

9b025fe9972f686e40481d5eb03518e2fdac2d14












springbok hardcoded path for registration
2012-10-05T17:30:34+00:00

kali
kali@leap.se

2012-10-05T17:30:34+00:00

f60e4bbbad22d6ae2d40abfc6f47eba1d0d7cbc8












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

kali
kali@leap.se

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

0576427f697fa631d8f5cc2fc596c60bce38dda3












remove test resources
2012-10-05T02:13:56+00:00

kali
kali@leap.se

2012-10-05T02:13:56+00:00

bcee816de0a68d21a91e45c894088c2e34eacf31












add menu for running wizard at will
2012-10-05T01:10:04+00:00

kali
kali@leap.se

2012-10-05T01:10:04+00:00

3e2eb0cb1878a9494650ea1278ef2f9211ebdaac

it's still buggy in that it does not bother to stop
the ongoing checks or connection. we should take care of that soon.





it's still buggy in that it does not bother to stop
the ongoing checks or connection. we should take care of that soon.







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.







remove prints
2012-10-04T22:13:48+00:00

kali
kali@leap.se

2012-10-04T22:13:48+00:00

baefda49d741a6e8149233f292f92221aaf3b675