bitmask-dev.git - [bitmask-dev]

Age	Commit message (Collapse)	Author
2012-10-26	user credentials saved on login/signup branches.	kali
	cert request is using magick decorator that retrieves the certificates using srp.
2012-10-25	login branch in wizard	kali

2012-10-24	last page of wizard displays the connection steps	kali

2012-10-24	sign up branch ends by triggering eip connection	kali
	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-20	password confirmation	kali

2012-10-20	add bypass for already trusted fingerprints	kali

2012-10-20	connecting page	kali
	and changes to functions having to do with the default path to certs.
2012-10-19	add bug number in log for #638 cases (domain name mismatch)	kali

2012-10-19	ca cert fingerprint check + api cert verification	kali

2012-10-19	download ca cert from provider	kali

2012-10-19	logic for cert validation widgets in wizard	kali

2012-10-18	catch cert verification errors and ask user for trust	kali
	with a little helper function using gnutls
2012-10-17	moved srp registration to base	kali
	and some minor changes in wizard, like textentry for provider.
2012-10-17	added skeleton for generic client wizard flow	kali

2012-10-11	comment out the set_password call until we fix #744	kali

2012-10-10	add feedback for connection error during signup	kali
	Closes #724
2012-10-08	catch timeout and specify kind of signup error	kali

2012-10-08	fix hexlify + add regex validator for usernames	kali

2012-10-06	springbok hardcoded path for registration	kali

2012-10-06	pep8	kali

2012-10-05	remove test resources	kali

2012-10-05	add menu for running wizard at will	kali
	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-05	use keyring to store user password	kali
	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-05	remove prints	kali

2012-10-05	use leap logo	kali

2012-10-05	focus fix for wizard	kali

2012-10-05	wizard called from main app if not run before.	kali

2012-10-05	add user registration to wizard	kali
	validation still a bit fragile but there it is.
2012-10-04	manual test	kali

2012-10-04	initial skeleton for wizard	kali

2012-09-20	fix resources test for hash	kali

2012-09-13	add leap logo	kali

2012-08-09	updated resource	kali

2012-08-09	re-added missing mainwindow_rc	kali

2012-08-08	test for hash of the resources file	kali
	this extra step might help avoiding accidental updates, /methinks
2012-07-23	update resource file	kali

2012-07-22	initial import	kali