android-passwordsafe - Project Hosting on Google Code

Last 7 days Dec 16, 2009 ImportExport (How-to Import/Export your password data into Android Passwor...) Wiki page commented on by gunderstorm - Did it occur to you people to research the name of your product? Good luck ALWAYS being asked if you are compatible with the (VERY awesome) original PasswordSafe, geniuses. Seriously, you are never going to escape this. You may as well embrace it. There are two Password Safes in the Android Market right now. Did it occur to you people to research the name of your product? Good luck ALWAYS being asked if you are compatible with the (VERY awesome) original PasswordSafe, geniuses. Seriously, you are never going to escape this. You may as well embrace it. There are two Password Safes in the Android Market right now. Earlier this year Jun 12, 2009 issue 1 (Make password safe entries searchable) commented on by dechellycanyon - Search function would greatly improved the usability of this great application. I've got close to 200 entries... Search function would greatly improved the usability of this great application. I've got close to 200 entries... Feb 03, 2009 issue 34 (Have the ability to have a text field, not just a "user name...) commented on by krank13 - This work-around is NOT quite as nice as a large text field, but now that the project has moved over to OI Safe and OI Notepad can be encrypted using OI Safe, you can encrypt items in notepad. It basically does what I wanted. I figured I would pass this work-around on. This work-around is NOT quite as nice as a large text field, but now that the project has moved over to OI Safe and OI Notepad can be encrypted using OI Safe, you can encrypt items in notepad. It basically does what I wanted. I figured I would pass this work-around on. Feb 02, 2009 issue 37 (Safe should be locked when app closes or phone is going into...) reported by felix.knecht - It really would help security a lot, when the safe is locked automatically in the following cases: - after a certain time - immediately when I switch to another app or to the home screen - phone goes into "suspend" (red button pressed) Maybe even make it configurable. This should automatically save all changes first, so no data is lost! It really would help security a lot, when the safe is locked automatically in the following cases: - after a certain time - immediately when I switch to another app or to the home screen - phone goes into "suspend" (red button pressed) Maybe even make it configurable. This should automatically save all changes first, so no data is lost! Feb 02, 2009 issue 36 (Should not discard on back button) reported by felix.knecht - What steps will reproduce the problem? 1. Add password 2. Enter data 3. Accidentally press back hardware button What is the expected output? What do you see instead? Changed/New entry won't be saved. I would expect to be at least asked if I really don't want to save the changes. This is VERY bad if you just created an account using the "generate password" functionality and hit the back button... So please add a "Are you sure" dialog or just save the changes (like the contact app does). The latter would require a discard button in the UI though. What steps will reproduce the problem? 1. Add password 2. Enter data 3. Accidentally press back hardware button What is the expected output? What do you see instead? Changed/New entry won't be saved. I would expect to be at least asked if I really don't want to save the changes. This is VERY bad if you just created an account using the "generate password" functionality and hit the back button... So please add a "Are you sure" dialog or just save the changes (like the contact app does). The latter would require a discard button in the UI though. Feb 02, 2009 issue 34 (Have the ability to have a text field, not just a "user name...) commented on by felix.knecht - I can only second the request from krank13. It would be nice to have an option in the settings to ONLY display the notes textbox and nothing else. Well, except the URL field, so you can find the entry in the list overview. This is much more how I work with password managers, because I also save tons of other stuff (and often not even username and password). I can only second the request from krank13. It would be nice to have an option in the settings to ONLY display the notes textbox and nothing else. Well, except the URL field, so you can find the entry in the list overview. This is much more how I work with password managers, because I also save tons of other stuff (and often not even username and password). Jan 26, 2009 issue 1 (Make password safe entries searchable) commented on by Peugeot50589 - I'd have to agree with this feature request. As it is now, your only view of passwords in PasswordSafe is via the Category and in most password programs categories are like "tags" and very random in how they're assigned, enforces, interpreted and adopted. Never thought it would get like this, but I've got 145 sites/passwords. I'm sure that there are others with multiples of that. So, you app is very important. Thank you for your hard work! I'd have to agree with this feature request. As it is now, your only view of passwords in PasswordSafe is via the Category and in most password programs categories are like "tags" and very random in how they're assigned, enforces, interpreted and adopted. Never thought it would get like this, but I've got 145 sites/passwords. I'm sure that there are others with multiples of that. So, you app is very important. Thank you for your hard work! Jan 23, 2009 issue 15 (Make Android Password Safe useful to other applications) commented on by egaskill - I've been waiting for a feature like this for awhile. A keychain type app that allows other apps to pull login information for stuff like facebook, twitter, etc. Also, might I suggest that you allow for a variable number of fields for information, instead of just doing a username and password field. That way other applications can pull not just username and login, but things like display name, account number, security question answers. I have a little bit of a SQL background if you'd like some suggestions on database layout as well. I've been waiting for a feature like this for awhile. A keychain type app that allows other apps to pull login information for stuff like facebook, twitter, etc. Also, might I suggest that you allow for a variable number of fields for information, instead of just doing a username and password field. That way other applications can pull not just username and login, but things like display name, account number, security question answers. I have a little bit of a SQL background if you'd like some suggestions on database layout as well. Jan 20, 2009 issue 34 (Have the ability to have a text field, not just a "user name...) commented on by f...@fuxoft.cz - I am using version 0.5 and it definitely has multi-line "Notes" field (encrypted). I am using version 0.5 and it definitely has multi-line "Notes" field (encrypted). Jan 20, 2009 issue 34 (Have the ability to have a text field, not just a "user name...) reported by krank13 - I know that there is a line of "notes" but it would be nice to be able to have JUST a text box, and nothing else. I work in IT, and would like to have a place to list all of my servers, and I would prefer it to be behind encryption. My document also has notes that pertain to the servers... that are not just username/passwords. Having a text field that I can replicate this information into, and carry around would be really nice. I know that there is a line of "notes" but it would be nice to be able to have JUST a text box, and nothing else. I work in IT, and would like to have a place to list all of my servers, and I would prefer it to be behind encryption. My document also has notes that pertain to the servers... that are not just username/passwords. Having a text field that I can replicate this information into, and carry around would be really nice. Jan 20, 2009 issue 33 (Possibility to user keyboard-less authentication?) commented on by catslaugh - The “Security & location” settings have an option to use a pattern where you connect the dots on a 3×3 grid; is that exported from a library where it would be easy to incorporate? The “Security & location” settings have an option to use a pattern where you connect the dots on a 3×3 grid; is that exported from a library where it would be easy to incorporate? Jan 14, 2009 r98 (Added PreferencesActivity with two preferences: external_acc...) committed by rmceoin - Added PreferencesActivity with two preferences: external_access and lock_timeout Added PreferencesActivity with two preferences: external_access and lock_timeout Jan 12, 2009 r97 (Merged trunk revisions 80, 82 and 85. ) committed by rmceoin - Merged trunk revisions 80, 82 and 85. Merged trunk revisions 80, 82 and 85. Jan 11, 2009 issue 33 (Possibility to user keyboard-less authentication?) Labels changed by rmceoin - Actually, I've wanted to create a 10-key entry for digit-only passwords. That'd be easy to do. Just need some time. Labels: Type-Enhancement −Type-Defect Actually, I've wanted to create a 10-key entry for digit-only passwords. That'd be easy to do. Just need some time. Labels: Type-Enhancement −Type-Defect Jan 11, 2009 r96 (Update CryptoIntents) committed by peli0101 - Update CryptoIntents Update CryptoIntents Jan 11, 2009 r95 (Add new broadcast action when user is logged out of service.) committed by peli0101 - Add new broadcast action when user is logged out of service. Add new broadcast action when user is logged out of service. Jan 10, 2009 issue 33 (Possibility to user keyboard-less authentication?) commented on by f...@fuxoft.cz - Sorry, I know this is not a "defect" but I don't see any option here to mark it as "Enhancement"... Sorry, I know this is not a "defect" but I don't see any option here to mark it as "Enhancement"... Jan 10, 2009 issue 33 (Possibility to user keyboard-less authentication?) reported by f...@fuxoft.cz - The Password Safe is mostly used to LOOK AT the stored password, not to enter the new ones, and in this case I need to open Android's keyboard just to enter the master password. Would it be hard to allow other method of master authentication, e.g. something similar to "gestures" used to lock the Android screen? The Password Safe is mostly used to LOOK AT the stored password, not to enter the new ones, and in this case I need to open Android's keyboard just to enter the master password. Would it be hard to allow other method of master authentication, e.g. something similar to "gestures" used to lock the Android screen? Jan 06, 2009 issue 32 (crashes on Go button click) commented on by rmceoin - The crashing was fixed in 0.5.0. The problem is that the correct format is "http://www.paypal.com" not "www.paypal.com". Prepend the "http:// and it'll work. The crashing was fixed in 0.5.0. The problem is that the correct format is "http://www.paypal.com" not "www.paypal.com". Prepend the "http:// and it'll work. Jan 06, 2009 issue 31 (Error "First line is missing fields" when importing csv file) Labels changed by rmceoin - Android Password Safe is not directly compatible with Windows Password Safe. They are two unrelated projects. You need to create some data within Android Password Safe, if you haven't done so already. Then Menu -> Export Database. This will create a file /sdcard/passwordsafe.csv Connect your G1 to your PC and grab the APWS created passwordsafe.csv. You need to make your .CSV match the created .CSV. Make sure you've read the Wiki page on the topic: http://code.google.com/p/android-passwordsafe/wiki/ImportExport Labels: Type-Other −Type-Defect Android Password Safe is not directly compatible with Windows Password Safe. They are two unrelated projects. You need to create some data within Android Password Safe, if you haven't done so already. Then Menu -> Export Database. This will create a file /sdcard/passwordsafe.csv Connect your G1 to your PC and grab the APWS created passwordsafe.csv. You need to make your .CSV match the created .CSV. Make sure you've read the Wiki page on the topic: http://code.google.com/p/android-passwordsafe/wiki/ImportExport Labels: Type-Other −Type-Defect Jan 05, 2009 r94 (updated diagrams with new extra names, permission lists, and...) committed by isaac.jones - updated diagrams with new extra names, permission lists, and EXTRA_TEXT_ARRAY updated diagrams with new extra names, permission lists, and EXTRA_TEXT_ARRAY Jan 05, 2009 issue 31 (Error "First line is missing fields" when importing csv file) commented on by gary.oberbrunner - This is expected behavior. The first line of your passwordsafe.csv should contain the fieldnames. (I know because I just imported all 256 of my passwords from SPB Wallet by writing a custom python script.) This is expected behavior. The first line of your passwordsafe.csv should contain the fieldnames. (I know because I just imported all 256 of my passwords from SPB Wallet by writing a custom python script.) Jan 05, 2009 r93 (Removed the ugly hack of using category for package name, ad...) committed by isaac.jones - Removed the ugly hack of using category for package name, added permission list, which involvd lots of changes. Added some fields to the database: - one for passwords, unique_name, which should eventually be guarenteed to be unique, so the client can look up names by, ie "org.syntaxpolice.opensocial" - A table for PACKAGE_ACCESS, a pairing of id to string indicating a list of packages which have access to the given password. Plus lots of plumbing to make this work. Changd some EXTRA names and removed category from extra: org.openintents.extra.UNIQUE_NAME Category is now Application Data. Bumped database version to 4, not sure if that's the right thing to do? DATABASE_VERSION = 4; Removed the ugly hack of using category for package name, added permission list, which involvd lots of changes. Added some fields to the database: - one for passwords, unique_name, which should eventually be guarenteed to be unique, so the client can look up names by, ie "org.syntaxpolice.opensocial" - A table for PACKAGE_ACCESS, a pairing of id to string indicating a list of packages which have access to the given password. Plus lots of plumbing to make this work. Changd some EXTRA names and removed category from extra: org.openintents.extra.UNIQUE_NAME Category is now Application Data. Bumped database version to 4, not sure if that's the right thing to do? DATABASE_VERSION = 4; Jan 03, 2009 issue 32 (crashes on Go button click) reported by dankelly613 - What steps will reproduce the problem? 1. create new password record with url 2. ex. www.paypal.com 3. click "Go" button What is the expected output? - visit website in default browser What do you see instead? - crashes and asks for forced close What version of the product are you using? ??? installed from app market 01/03/09 On what operating system? ??? android G1 phone purchased 01/02/09 Please provide any additional information below. What steps will reproduce the problem? 1. create new password record with url 2. ex. www.paypal.com 3. click "Go" button What is the expected output? - visit website in default browser What do you see instead? - crashes and asks for forced close What version of the product are you using? ??? installed from app market 01/03/09 On what operating system? ??? android G1 phone purchased 01/02/09 Please provide any additional information below. Jan 03, 2009 issue 31 (Error "First line is missing fields" when importing csv file) reported by nigel.c.lee - What steps will reproduce the problem? 1. Export csv file from Password Safe version 2.06 Beta on Windows XP Pro SP2 2. Copy csv file to Android (G1) SD card 3. Import csv file to Password Safe on Android (G1) What is the expected output? What do you see instead? Expect password data should be available on G1. Instead receive error message "First line is missing fields" What version of the product are you using? On what operating system? Windows XP Professional: 2.06 Beta Android: 0.5.0 Please provide any additional information below. What steps will reproduce the problem? 1. Export csv file from Password Safe version 2.06 Beta on Windows XP Pro SP2 2. Copy csv file to Android (G1) SD card 3. Import csv file to Password Safe on Android (G1) What is the expected output? What do you see instead? Expect password data should be available on G1. Instead receive error message "First line is missing fields" What version of the product are you using? On what operating system? Windows XP Professional: 2.06 Beta Android: 0.5.0 Please provide any additional information below. Jan 03, 2009 r92 (Adjust lock layout. Finish on lock through notification.) committed by peli0101 - Adjust lock layout. Finish on lock through notification. Adjust lock layout. Finish on lock through notification. Jan 02, 2009 r91 (slightly better screenshot) committed by isaac.jones - slightly better screenshot slightly better screenshot Jan 02, 2009 r90 (screenshot for encrypting a note) committed by isaac.jones - screenshot for encrypting a note screenshot for encrypting a note Jan 02, 2009 r89 (diagrams explaining the intents, using dia format.) committed by isaac.jones - diagrams explaining the intents, using dia format. diagrams explaining the intents, using dia format. Jan 02, 2009 r88 (Update intents class in test app.) committed by peli0101 - Update intents class in test app. Update intents class in test app. Jan 02, 2009 r87 (Added support for EXTRA_TEXT_ARRAY, so that multiple strings...) committed by peli0101 - Added support for EXTRA_TEXT_ARRAY, so that multiple strings can be encrypted / decrypted in a single intent call. Added support for EXTRA_TEXT_ARRAY, so that multiple strings can be encrypted / decrypted in a single intent call. Jan 01, 2009 r86 (Added screen for the notification activity to log the user o...) committed by isaac.jones - Added screen for the notification activity to log the user out. There's still an issue with the category list remembering the password at this point, and we need to make it forget because the "back" button allows you to get to the passwords still. Added screen for the notification activity to log the user out. There's still an issue with the category list remembering the password at this point, and we need to make it forget because the "back" button allows you to get to the passwords still. Jan 01, 2009 issue 26 (after import, offer to delete csv) Status changed by rmceoin - Added in R85. Status: Fixed Added in R85. Status: Fixed Jan 01, 2009 r85 (Added an Alert to ask user if they want to delete the CSV af...) committed by rmceoin - Added an Alert to ask user if they want to delete the CSV after a successful import. Addresses I26. Added an Alert to ask user if they want to delete the CSV after a successful import. Addresses I26. Jan 01, 2009 r84 (Added explanation in the case where apws is started remotely...) committed by isaac.jones - Added explanation in the case where apws is started remotely, <string name="remote_ask">Another application is asking to use the master key. Please type in your password to unlock it.</string> Added explanation in the case where apws is started remotely, <string name="remote_ask">Another application is asking to use the master key. Please type in your password to unlock it.</string> Jan 01, 2009 r83 (handle error case) committed by isaac.jones - handle error case handle error case Older Dec 31, 2008 r82 (Updated Help to talk about Master Password. Changed labels ...) committed by rmceoin - Updated Help to talk about Master Password. Changed labels to use 'Master Password'. Updated Help to talk about Master Password. Changed labels to use 'Master Password'. Dec 31, 2008 r81 (Merged r64 from the service branch. ) committed by rmceoin - Merged r64 from the service branch. Merged r64 from the service branch. Dec 31, 2008 issue 28 (Allow moving password entries between categories) Status changed by rmceoin - Status: Done Status: Done Dec 31, 2008 issue 28 (Allow moving password entries between categories) commented on by rmceoin - Added in r80. Added in r80. Dec 31, 2008 r80 (Added the ability to move passwords to another category. ) committed by rmceoin - Added the ability to move passwords to another category. Added the ability to move passwords to another category. Dec 31, 2008 r79 (Add notification symbol to notification bar while user is lo...) committed by peli0101 - Add notification symbol to notification bar while user is logged in. Add notification symbol to notification bar while user is logged in. Dec 31, 2008 r78 (Move service classes to separate package.) committed by peli0101 - Move service classes to separate package. Move service classes to separate package. Dec 30, 2008 r77 (Move intents actions and extras into the OpenIntents package...) committed by peli0101 - Move intents actions and extras into the OpenIntents package name space.Remove "text/plain" requirement in crypto intents. getType() usually refers to the type passed in getData(), but in this case, extras are used with well-defined type. Also, in FrontDoor, when returning an intent, make sure that all additional extras passed in the first place are returned unmodified. This makes it possible for third party applications to add additional information about the text that has been encrypted. Move intents actions and extras into the OpenIntents package name space.Remove "text/plain" requirement in crypto intents. getType() usually refers to the type passed in getData(), but in this case, extras are used with well-defined type. Also, in FrontDoor, when returning an intent, make sure that all additional extras passed in the first place are returned unmodified. This makes it possible for third party applications to add additional information about the text that has been encrypted. Dec 30, 2008 issue 15 (Make Android Password Safe useful to other applications) commented on by isaac.jones - And the constants kinda provide an explanation of what's done at this point: /** * Activity Action: Encrypt the string given in the extra TEXT. * Returns the encrypted string in the extra TEXT. * * <p>Constant Value: "org.openintents.action.ENCRYPT"</p> / public static final String ACTION_ENCRYPT = "org.openintents.action.ENCRYPT"; /* * Activity Action: Decrypt the string given in the extra TEXT. * Returns the decrypted string in the extra TEXT. * * <p>Constant Value: "org.openintents.action.DECRYPT"</p> / public static final String ACTION_DECRYPT = "org.openintents.action.DECRYPT"; /* * Activity Action: Get the password corresponding to the category of the * calling application, and the EXTRA_DESCRIPTION, as provided. * Returns the decrypted username & password in the extras EXTRA_USERNAME and * EXTRA_PASSWORD. CATEGORY is an optional parameter. * * <p>Constant Value: "org.openintents.action.GET_PASSWORD"</p> / public static final String ACTION_GET_PASSWORD = "org.openintents.action.GET_PASSWORD"; /* * Activity Action: Set the password corresponding to the category of the * calling application, and the EXTRA_DESCRIPTION, EXTRA_USERNAME and * EXTRA_PASSWORD as provided. CATEGORY is an optional parameter. * * If both username and password are the non-null empty string, delete this * password entry. * <p>Constant Value: "org.openintents.action.SET_PASSWORD"</p> / public static final String ACTION_SET_PASSWORD = "org.openintents.action.SET_PASSWORD"; /* * The text to encrypt or decrypt, or the location for the return result. * * <p>Constant Value: "org.openintents.extra.TEXT"</p> / public static final String EXTRA_TEXT = "org.openintents.extra.TEXT"; /* * Required input parameter to GET_PASSWORD and SET_PASSWORD. Corresponds to the "description" * field in passwordsafe. Should be a descriptive name for the password you're using, * and will already be specific to your application. * * <p>Constant Value: "org.openintents.extra.DESCRIPTION"</p> / public static final String EXTRA_DESCRIPTION = "org.openintents.extra.DESCRIPTION"; /* * Optional input parameter to GET_PASSWORD and SET_PASSWORD. Corresponds to the "category" * field in passwordsafe. If null, will be assumed to be the fully-qualified package * name of your application. If non-null (and not == the package name) the user should * be asked whether it's permissable to get or set this password. * * <p>Constant Value: "org.openintents.extra.CATEGORY"</p> / public static final String EXTRA_CATEGORY = "org.openintents.extra.CATEGORY"; /* * Output parameter from GET_PASSWORD and input parameter to SET_PASSWORD. * Corresponds to the decrypted "username" field in passwordsafe. * * <p>Constant Value: "org.openintents.extra.USERNAME"</p> / public static final String EXTRA_USERNAME = "org.openintents.extra.USERNAME"; /* * Output parameter from GET_PASSWORD and input parameter to SET_PASSWORD. * Corresponds to the decrypted "password" field in passwordsafe. * * <p>Constant Value: "org.openintents.extra.PASSWORD"</p> / public static final String EXTRA_PASSWORD = "org.openintents.extra.PASSWORD"; And the constants kinda provide an explanation of what's done at this point: /* * Activity Action: Encrypt the string given in the extra TEXT. * Returns the encrypted string in the extra TEXT. * * <p>Constant Value: "org.openintents.action.ENCRYPT"</p> / public static final String ACTION_ENCRYPT = "org.openintents.action.ENCRYPT"; /* * Activity Action: Decrypt the string given in the extra TEXT. * Returns the decrypted string in the extra TEXT. * * <p>Constant Value: "org.openintents.action.DECRYPT"</p> / public static final String ACTION_DECRYPT = "org.openintents.action.DECRYPT"; /* * Activity Action: Get the password corresponding to the category of the * calling application, and the EXTRA_DESCRIPTION, as provided. * Returns the decrypted username & password in the extras EXTRA_USERNAME and * EXTRA_PASSWORD. CATEGORY is an optional parameter. * * <p>Constant Value: "org.openintents.action.GET_PASSWORD"</p> / public static final String ACTION_GET_PASSWORD = "org.openintents.action.GET_PASSWORD"; /* * Activity Action: Set the password corresponding to the category of the * calling application, and the EXTRA_DESCRIPTION, EXTRA_USERNAME and * EXTRA_PASSWORD as provided. CATEGORY is an optional parameter. * * If both username and password are the non-null empty string, delete this * password entry. * <p>Constant Value: "org.openintents.action.SET_PASSWORD"</p> / public static final String ACTION_SET_PASSWORD = "org.openintents.action.SET_PASSWORD"; /* * The text to encrypt or decrypt, or the location for the return result. * * <p>Constant Value: "org.openintents.extra.TEXT"</p> / public static final String EXTRA_TEXT = "org.openintents.extra.TEXT"; /* * Required input parameter to GET_PASSWORD and SET_PASSWORD. Corresponds to the "description" * field in passwordsafe. Should be a descriptive name for the password you're using, * and will already be specific to your application. * * <p>Constant Value: "org.openintents.extra.DESCRIPTION"</p> / public static final String EXTRA_DESCRIPTION = "org.openintents.extra.DESCRIPTION"; /* * Optional input parameter to GET_PASSWORD and SET_PASSWORD. Corresponds to the "category" * field in passwordsafe. If null, will be assumed to be the fully-qualified package * name of your application. If non-null (and not == the package name) the user should * be asked whether it's permissable to get or set this password. * * <p>Constant Value: "org.openintents.extra.CATEGORY"</p> / public static final String EXTRA_CATEGORY = "org.openintents.extra.CATEGORY"; /* * Output parameter from GET_PASSWORD and input parameter to SET_PASSWORD. * Corresponds to the decrypted "username" field in passwordsafe. * * <p>Constant Value: "org.openintents.extra.USERNAME"</p> / public static final String EXTRA_USERNAME = "org.openintents.extra.USERNAME"; /* * Output parameter from GET_PASSWORD and input parameter to SET_PASSWORD. * Corresponds to the decrypted "password" field in passwordsafe. * * <p>Constant Value: "org.openintents.extra.PASSWORD"</p> */ public static final String EXTRA_PASSWORD = "org.openintents.extra.PASSWORD"; Dec 30, 2008 issue 15 (Make Android Password Safe useful to other applications) commented on by isaac.jones - Lots done already. Here's what's left: - A status bar indicating whether or not passwordsafe is unlocked, with the ability, most likely, to see how long it'll be unlocked for, and to re-lock it. - A preference capability to set the lock timeout, with the possibility that it's zero. - Decisions on the security permissions required. - SET_PASSWORD - a field entry in the database for "invisible" or "locked" passwords that either aren't shown to users, or can't be edited by users (but probably can be deleted). These are the passwords that are created programatically by other applications using SET_PASSWORD. - An entry in the database for which applications are permitted to get & set a password (defaults to the category == package name), plus the user interface for this capability - Lots of little things noted as TODOs in the code. - Probably a write-up and request for vetting - Perhaps the ability to generate "cooler" keys, like certificate keypairs and to sign stuff with them, but that's down the road. - The ability to process larger chunks of data than string extras. - Maybe convert categories to tags? - Maybe Lots done already. Here's what's left: - A status bar indicating whether or not passwordsafe is unlocked, with the ability, most likely, to see how long it'll be unlocked for, and to re-lock it. - A preference capability to set the lock timeout, with the possibility that it's zero. - Decisions on the security permissions required. - SET_PASSWORD - a field entry in the database for "invisible" or "locked" passwords that either aren't shown to users, or can't be edited by users (but probably can be deleted). These are the passwords that are created programatically by other applications using SET_PASSWORD. - An entry in the database for which applications are permitted to get & set a password (defaults to the category == package name), plus the user interface for this capability - Lots of little things noted as TODOs in the code. - Probably a write-up and request for vetting - Perhaps the ability to generate "cooler" keys, like certificate keypairs and to sign stuff with them, but that's down the road. - The ability to process larger chunks of data than string extras. - Maybe convert categories to tags? - Maybe Dec 29, 2008 r76 (added special case for empty username and password to delete...) committed by isaac.jones - added special case for empty username and password to delete the given password. added special case for empty username and password to delete the given password. Dec 29, 2008 r75 (Added SetPassword implementation. Open question: Should we ...) committed by isaac.jones - Added SetPassword implementation. Open question: Should we provide extras for all of the fields for a password entry? Modified addCategory to dbHelper to NOT add a category if one with the same name already exists. This simplified the logic in some spots. Test driver has new fields to set description / usernmae / password. You can use these with 'set' button to add a password, then query it with "get". Added SetPassword implementation. Open question: Should we provide extras for all of the fields for a password entry? Modified addCategory to dbHelper to NOT add a category if one with the same name already exists. This simplified the logic in some spots. Test driver has new fields to set description / usernmae / password. You can use these with 'set' button to add a password, then query it with "get". Dec 29, 2008 issue 30 (add version info in help screen) changed by rmceoin - Status: Accepted Labels: Type-Enhancement −Type-Defect Status: Accepted Labels: Type-Enhancement −Type-Defect Dec 29, 2008 issue 29 (add version info in help screen) Status changed by rmceoin - Status: Duplicate Status: Duplicate

issue 15 (Make Android Password Safe useful to other applications) commented on by isaac.jones - And the constants kinda provide an explanation of what's done at this point: /** * Activity Action: Encrypt the string given in the extra TEXT. * Returns the encrypted string in the extra TEXT. * * Constant Value: "org.openintents.action.ENCRYPT" */ public static final String ACTION_ENCRYPT = "org.openintents.action.ENCRYPT"; /** * Activity Action: Decrypt the string given in the extra TEXT. * Returns the decrypted string in the extra TEXT. * * Constant Value: "org.openintents.action.DECRYPT" */ public static final String ACTION_DECRYPT = "org.openintents.action.DECRYPT"; /** * Activity Action: Get the password corresponding to the category of the * calling application, and the EXTRA_DESCRIPTION, as provided. * Returns the decrypted username & password in the extras EXTRA_USERNAME and * EXTRA_PASSWORD. CATEGORY is an optional parameter. * * Constant Value: "org.openintents.action.GET_PASSWORD" */ public static final String ACTION_GET_PASSWORD = "org.openintents.action.GET_PASSWORD"; /** * Activity Action: Set the password corresponding to the category of the * calling application, and the EXTRA_DESCRIPTION, EXTRA_USERNAME and * EXTRA_PASSWORD as provided. CATEGORY is an optional parameter. * * If both username and password are the non-null empty string, delete this * password entry. * Constant Value: "org.openintents.action.SET_PASSWORD" */ public static final String ACTION_SET_PASSWORD = "org.openintents.action.SET_PASSWORD"; /** * The text to encrypt or decrypt, or the location for the return result. * * Constant Value: "org.openintents.extra.TEXT" */ public static final String EXTRA_TEXT = "org.openintents.extra.TEXT"; /** * Required input parameter to GET_PASSWORD and SET_PASSWORD. Corresponds to the "description" * field in passwordsafe. Should be a descriptive name for the password you're using, * and will already be specific to your application. * * Constant Value: "org.openintents.extra.DESCRIPTION" */ public static final String EXTRA_DESCRIPTION = "org.openintents.extra.DESCRIPTION"; /** * Optional input parameter to GET_PASSWORD and SET_PASSWORD. Corresponds to the "category" * field in passwordsafe. If null, will be assumed to be the fully-qualified package * name of your application. If non-null (and not == the package name) the user should * be asked whether it's permissable to get or set this password. * * Constant Value: "org.openintents.extra.CATEGORY" */ public static final String EXTRA_CATEGORY = "org.openintents.extra.CATEGORY"; /** * Output parameter from GET_PASSWORD and input parameter to SET_PASSWORD. * Corresponds to the decrypted "username" field in passwordsafe. * * Constant Value: "org.openintents.extra.USERNAME" */ public static final String EXTRA_USERNAME = "org.openintents.extra.USERNAME"; /** * Output parameter from GET_PASSWORD and input parameter to SET_PASSWORD. * Corresponds to the decrypted "password" field in passwordsafe. * * Constant Value: "org.openintents.extra.PASSWORD" */ public static final String EXTRA_PASSWORD = "org.openintents.extra.PASSWORD";

And the constants kinda provide an explanation of what's done at this point: /** * Activity Action: Encrypt the string given in the extra TEXT. * Returns the encrypted string in the extra TEXT. * * Constant Value: "org.openintents.action.ENCRYPT" */ public static final String ACTION_ENCRYPT = "org.openintents.action.ENCRYPT"; /** * Activity Action: Decrypt the string given in the extra TEXT. * Returns the decrypted string in the extra TEXT. * * Constant Value: "org.openintents.action.DECRYPT" */ public static final String ACTION_DECRYPT = "org.openintents.action.DECRYPT"; /** * Activity Action: Get the password corresponding to the category of the * calling application, and the EXTRA_DESCRIPTION, as provided. * Returns the decrypted username & password in the extras EXTRA_USERNAME and * EXTRA_PASSWORD. CATEGORY is an optional parameter. * * Constant Value: "org.openintents.action.GET_PASSWORD" */ public static final String ACTION_GET_PASSWORD = "org.openintents.action.GET_PASSWORD"; /** * Activity Action: Set the password corresponding to the category of the * calling application, and the EXTRA_DESCRIPTION, EXTRA_USERNAME and * EXTRA_PASSWORD as provided. CATEGORY is an optional parameter. * * If both username and password are the non-null empty string, delete this * password entry. * Constant Value: "org.openintents.action.SET_PASSWORD" */ public static final String ACTION_SET_PASSWORD = "org.openintents.action.SET_PASSWORD"; /** * The text to encrypt or decrypt, or the location for the return result. * * Constant Value: "org.openintents.extra.TEXT" */ public static final String EXTRA_TEXT = "org.openintents.extra.TEXT"; /** * Required input parameter to GET_PASSWORD and SET_PASSWORD. Corresponds to the "description" * field in passwordsafe. Should be a descriptive name for the password you're using, * and will already be specific to your application. * * Constant Value: "org.openintents.extra.DESCRIPTION" */ public static final String EXTRA_DESCRIPTION = "org.openintents.extra.DESCRIPTION"; /** * Optional input parameter to GET_PASSWORD and SET_PASSWORD. Corresponds to the "category" * field in passwordsafe. If null, will be assumed to be the fully-qualified package * name of your application. If non-null (and not == the package name) the user should * be asked whether it's permissable to get or set this password. * * Constant Value: "org.openintents.extra.CATEGORY" */ public static final String EXTRA_CATEGORY = "org.openintents.extra.CATEGORY"; /** * Output parameter from GET_PASSWORD and input parameter to SET_PASSWORD. * Corresponds to the decrypted "username" field in passwordsafe. * * Constant Value: "org.openintents.extra.USERNAME" */ public static final String EXTRA_USERNAME = "org.openintents.extra.USERNAME"; /** * Output parameter from GET_PASSWORD and input parameter to SET_PASSWORD. * Corresponds to the decrypted "password" field in passwordsafe. * * Constant Value: "org.openintents.extra.PASSWORD" */ public static final String EXTRA_PASSWORD = "org.openintents.extra.PASSWORD";

Last 7 days

Earlier this year

Older