summaryrefslogtreecommitdiff
path: root/src/leap/gui
AgeCommit message (Collapse)Author
2012-10-26user credentials saved on login/signup branches.kali
cert request is using magick decorator that retrieves the certificates using srp.
2012-10-25login branch in wizardkali
2012-10-24last page of wizard displays the connection stepskali
2012-10-24sign up branch ends by triggering eip connectionkali
still need to bind signals properly, and block on the validation process until we receive the "connected" signal. but the basic flow is working again, i.e, user should be able to remove the .config/leap folder and get all the needed info from the provider.
2012-10-20password confirmationkali
2012-10-20add bypass for already trusted fingerprintskali
2012-10-20connecting pagekali
and changes to functions having to do with the default path to certs.
2012-10-19add bug number in log for #638 cases (domain name mismatch)kali
2012-10-19ca cert fingerprint check + api cert verificationkali
2012-10-19download ca cert from providerkali
2012-10-19logic for cert validation widgets in wizardkali
2012-10-18catch cert verification errors and ask user for trustkali
with a little helper function using gnutls
2012-10-17moved srp registration to basekali
and some minor changes in wizard, like textentry for provider.
2012-10-17added skeleton for generic client wizard flowkali
2012-10-11comment out the set_password call until we fix #744kali
2012-10-10add feedback for connection error during signupkali
Closes #724
2012-10-08catch timeout and specify kind of signup errorkali
2012-10-08fix hexlify + add regex validator for usernameskali
2012-10-06springbok hardcoded path for registrationkali
2012-10-06pep8kali
2012-10-05remove test resourceskali
2012-10-05add menu for running wizard at willkali
it's still buggy in that it does not bother to stop the ongoing checks or connection. we should take care of that soon.
2012-10-05use keyring to store user passwordkali
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.
2012-10-05remove printskali
2012-10-05use leap logokali
2012-10-05focus fix for wizardkali
2012-10-05wizard called from main app if not run before.kali
2012-10-05add user registration to wizardkali
validation still a bit fragile but there it is.
2012-10-04manual testkali
2012-10-04initial skeleton for wizardkali
2012-09-20fix resources test for hashkali
2012-09-13add leap logokali
2012-08-09updated resourcekali
2012-08-09re-added missing mainwindow_rckali
2012-08-08test for hash of the resources filekali
this extra step might help avoiding accidental updates, /methinks
2012-07-23update resource filekali
2012-07-22initial importkali