PasswordMaker Forums
Other Editions => Other Editions - Help and Support => Topic started by: jstapleton on August 16, 2011, 02:09:49 AM
-
I recently got a Motorola Atrix that runs Android, so I ported my iPhone app to the Android platform. You can download it here:
https://market.android.com/details?id=org.passwordmaker.android (https://market.android.com/details?id=org.passwordmaker.android)
I will continue to maintain the iPhone version for the time being
-
Wiki updated. Now I need to update the wiki software so that it can be opened for editing again. Maybe I'll find time this weekend.
-
Wiki updated. Now I need to update the wiki software so that it can be opened for editing again. Maybe I'll find time this weekend.
What? The wiki isn't editable? I don't understand.
-
I recently got a Motorola Atrix that runs Android, so I ported my iPhone app to the Android platform. You can download it here:
https://market.android.com/details?id=org.passwordmaker.android (https://market.android.com/details?id=org.passwordmaker.android)
I will continue to maintain the iPhone version for the time being
I've got an Android and installed it. Very nice! Funny how there are 2-3 clones in the Android Marketplace, none of which do anything like PasswordMaker. They just hijacked the name.
Eric
Creator - PasswordMaker
-
Bots were causing all sorts of issues, so I had stop allowing edits to the Wiki until I had time to upgrade the software installed. Never finished it though.
On my Backflip, trying to select HMAC-SHA256 crashes the app, I don't know if that applies to the other algorithms as my phone bricked itself over night, so I can't do any more testing. It might be trying to use too much memory for some reason.
-
Well, my replacement phone is an Atrix, and I still have issues with changing the algorithm.
-
I fixed the bug with the HMAC crashing.
Also added ability to edit the favorites
I'm still learning the Android API.
-
Now the HMAC bug moved to having a profile with it selected.I'm curious about how this happens.
-
My unit test only tested the layer of the hashing not of the profile. But the bug was I accidentally had the hmac digest size return the underling hash's blocksize instead. I must have thought I tested it in the app itself, but probably forgot to change the profile to the one I created for the hmac test, and just made sure it looked like it worked. This time I added a unit test + verify the result against the javascript version on the web.
The new version is now out on the Market.