bitmask_client.git - [bitmask

Age	Commit message (Collapse)	Author
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	todo comments	kali

2012-10-05	remove test resources	kali

2012-10-05	fix cert needed evaluation	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	init QSettings - save window geometry	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-10-02	moved eip checks to qthread to let icon show early	kali

2012-10-02	remove ui header	kali

2012-10-02	Merge branch 'feature/json-validation' into develop	kali
	Conflicts: src/leap/eip/config.py src/leap/eip/specs.py
2012-10-02	refactored jsonconfig, included jsonschema validation	kali
	and type casting.
2012-09-25	make test for provider pass	kali

2012-09-25	workaround for #638 and fix for eip config check for gateways	kali
	(we were picking gateway in a wrong way) Closes #610.
2012-09-25	fix slug for eip config	kali
	(was taking the one for eip-service) also correct the path (should be in root leap config folder).
2012-09-24	add schema to JSONLeapConfig classes	kali
	and a jsonvalidate function too, that calls to jsonchemea.validate(self, data) with self.schema We're using the specs to both purposes now: * providing a type casting system for our config options (work in progress for the type casting) * json schema validation
2012-09-24	fix slug for eip config	kali
	(was taking the one for eip-service) also correct the path (should be in root leap config folder).
2012-09-21	add property to baseconfig	kali
	config instead of get_config()
2012-09-21	added --no-provider-checks and --no-ca-verify for ease of debugging	kali
	Close #604
2012-09-20	Merge branch 'feature/remove-unity-checks' into develop	kali

2012-09-20	fix resources test for hash	kali

2012-09-20	add logging	kali

2012-09-20	cleanup	kali

2012-09-20	toggle connection on/off	kali

2012-09-20	start hidden, and toggle details window from menu	kali

2012-09-20	Merge branch 'develop' into feature/systray-menu	kali
	Conflicts: src/leap/app.py
2012-09-20	tests pass after branding changes	kali

2012-09-18	removed checks and changes involving systray-whitelist and unity because	antialias
	it works without them on Ubuntu 11.10 & 12.04.
2012-09-19	openvpn options come from eip.json	kali

2012-09-19	copy cacert to local config dir	kali

2012-09-19	checks for certificate	kali

2012-09-18	cert verification and malformed json checks	kali

2012-09-18	do_branding command added to setup	kali

2012-09-18	set app icon	kali
	(shows on window, minimized icons and about dialog)
2012-09-14	init icon	kali

2012-09-13	fix race condition on app init	kali
	still fragile; sometimes the qt app inits faster and make the send command miss the not yet created managemente socket.
2012-09-13	add leap logo	kali

2012-09-13	remove debug logging	kali

2012-09-13	display about and aboutqt dialogs	kali

2012-09-13	add versioneer	kali

2012-09-12	add openvpn-verb option to cli.	kali
	Closes #534. accepts int [1-6] that get passed to openvpn invocation. We should filter out the polling "state"/"status" commands from the log if we want it to be real useful.