leap_android.git - [leap

Age	Commit message (Collapse)	Author
2013-07-12	User messages are added to the new recovery dialog	Parménides GV
	When login is not successful, a new recovery dialog is prompted with a message about the previous error.
2013-07-12	Use anonymously from ProviderDetail works OK.	Parménides GV
	Tested with dev.bitmask.net, I use the previously downloaded certificate (I should not do that, I'll file an issue because I should download it once the user has requested to do so). Next step: login button from ProviderDetailFragment.
2013-07-12	Coded new fragment appearance	Parménides GV
	Domain, name and description come from provider.json Next step: code buttons to login or to use anonymously.
2013-06-20	User messages are now in string.xml	Parménides GV
	Some more constants added to ConfigHelper. This solves #2908.
2013-06-19	First round of comments.	Parménides GV
	This resolves the first step from issue #2908. Next step: Put user message strings into an appropiate place.
2013-06-08	Clean up some unused and some formatting	Sean Leonard

2013-06-08	Make LogInDialog accept passwords >= 8 characters, instead of > 8	Sean Leonard

2013-05-13	A bit more clean.	Parménides GV
	I've upper cased ConfigHelper constants. I've created a new method in ConfigHelper, to send requests to a server, that it's used when sending A and M1.
2013-04-29	Changed the message shown when checking if the password is valid or not.	Parménides GV
	Refactored LeapSRPSession so that there is no need to send A twice.
2013-04-29	"Trust completely" checkbox saves that trust for the new provider	Parménides GV
	entered, so that if in the future the client tries to log in or whatever, it can use the certificate downloaded when added. Log in dialog works ok, showing a toast when authentication fails (by this time, I have not managed to get a correct login due to dev.bitmask.net problems). dev.bitmask.net works perfectly, via adding it as a new provider (MeanderingCode, this is for you ;) ). All GET requests are done by default Android URL class, which means that certificates trusted by Android are also trusted by us. If there are problems when logging in due to certificates, the app is able to use only the certificate associated to the provider in the moment it was selected as the chosen provider.
2013-04-29	Added danger mode: we can bypass dev.bitmask.net hostname io exception.	Parménides GV

2013-04-29	Coded dialog (now there is a button in the Dashboard), time to test.	Parménides GV
	I need to implement bypass for dev.bitmask.net, because bitmask.net is down.