PasswordServant

Password Servant help

Scroll to read the help text. To return from the help text, please use the Android return button.

Content

Ch. 1 Overview

Ch. 2 Database management

Ch. 2.1 New user

Ch. 2.2 Backup database

Ch. 2.3 Restore database

Ch. 2.4 Delete user

Ch. 2.5 Batch input

Ch. 3 Password groups

Ch. 3.1 Web account

Ch. 3.2 Computer login

Ch. 3.3 Credit card

Ch. 3.4 Mail account

Ch. 3.5 Gate code

Ch. 3.6 Internal file encryption

Ch. 3.7 External file encryption

Ch. 3.8 Network login

Ch. 3.9 Userdefined password groups

Ch. 4 Use cases

Ch. 4.1 Password generation

Ch. 4.2 Secure sharing of files

Ch. 4.3 Optional password

Ch. 4.4 Inactivity timeout

Ch. 5 EULA FOR PS-Lite

Chapter 1 Overview

The PS-Lite by UBVASA securely stores your password information you need for accessing different services. You can create different users, with their own sets of securely stored password information. It can also generate random passwords for you, and it can encrypt/decrypt any file that you want to handle confidentially. It aims to do all of this in a minimalistic, but competent, style. The first time PS-Lite is started you have to enter a user name, and a login password. The password has to be entered two times, containing minimum six characters. There is no restriction on the number of times that one can try to login. However, after 3 unsuccessful attempts there will be a blocking period of 20 seconds before a new attempt to login can be done. After 10 unsuccessful attempts this blocking period is increased to 1 minute. This application uses the Linux security services accessible from the Android application environment, e.g. for encryption the AES cipher with 128-bit key length is used. This, together with the software security knowledge by the UBVASA developer, should yield a quite secure storage of your data. However, yuo should know that no cipher is unbreakable. And all security solutions can be hacked, given enough time and computing resources. So at the end it is up to you to prevent (too generous) exposure of your protected data to potential attackers. This application does not require any access to internet or telephony services, which should ease your fear that the program itself is a potential attacker:) PS-Lite is the free version of the application PasswordServant. The difference is that PS-Lite has a restriction on maximum 5 entries for each of the different password groups.

Chapter 2 Database management

After having logged in you can select "Database management" among the alternatives available on the spinner. This brings up a menu with four buttons, providing the services described in the coming chapters 2.1-2.4.

Chapter 2.1 New user

PS-Lite supports having multiple users, with separate user names and login passwords. This can e.g. be used for separating private and business password information, or for keeping your family members password information in a secure and structured way. Create a new user can only be done by an already existing user, after logging in. This brings up the new user menu, in which the new user name and login password is entered. You can of course hand over the phone to e.g. any of your family members to privately enter user name and login password. Please be aware of that this user can then let others become users also. Each user can however only access its own set of database information, so there is no security risk between users with having multiple users.

Chapter 2.2 Backup database

You can make a backup copy of the sqlite database that contains all the password information (for all users). Pushing this button leads to that a copy of the database becomes stored in the directory "/mnt/sdcard/Android/data/se.ubvasa.android.ps_lite/files/" (*) on the SD card, in a file named "passwordservant.db". You can then move this file to any other location, including sending it out of the phone. The data in the file is securely encrypted by using the AES cipher with 128-bit key length, so there is a very small security risk in storing this file in unsecure environments. The only information not encrypted are the name fields for the different password group entries, the edit date field, and the user names of the users of this application. If you are not satisfied with this security level, you can use the encryption service available in the "Internal file encryption" password group to add another round of encryption to the complete database file (see ch. 3.6). It is possible to use backup/restore to move the application database from PS-Lite to PasswordServant, if you decide to upgrade (see ch. 4.2). It is also possible to use backup/restore to move the database from one phone to another, provided that you have the application on both phones.

Chapter 2.3 Restore database

To restore a previously saved database, this file must first be placed in the directory "/mnt/sdcard/Android/data/se.ubvasa.android.ps_lite/files/" (*) on the SD card, and have the name "passwordservant.db". Please be aware that restoring the database from this file leads to that the existing application database gets deleted. So unless you do not want the content of that to be lost, you must first do a backup of it (see ch. 2.2).

Chapter 2.4 Delete user

A user can only be deleted when being logged in as this user, no user can delete any other user. Please be aware that all data saved in the database for this user becomes deleted, also the user login password and user name. There is no way to retrieve it, so please think an extra time before answering Yes in the dialog that pops up. The data for other users in the database is of course preserved.

Chapter 2.5 Batch input

You may have a lot of data that you want to enter into PasswordServant to begin with. To make this input more convenient, it is possible to enter this data into a file on your PC and then move the file to the PasswordServant directory on the phone, from where it can be read into the database. And once that is done, the file can be encrypted and moved back to your PC where it can be securely kept as an alternative backup (alternative to the databse backup, see ch. 2.2).

If you find this to be of interest, do as follows.

First go to the Database management menu, and push the 'Batch input' button. This will lead to that you are informed that no file exists, and asked if you want to generate a template file. Answering Yes on that will lead to that a file named PS_BatchInputData.csv is generated in the directory "/mnt/sdcard/Android/data/se.ubvasa2.android.ps_lite/files/" (*) on the SD card (we are assuming here that there does not already exist a file with that name).

Move this file to your PC (e.g. by using the "My files" app to mail it to yourself, or transfer it over USB), and on the PC just click on it. As this file is a comma delimited CSV file, it will automatically be opened by your standard spread sheet program (e.g. LibreOffice Calc, or Excel).

You will now see a number of rows of which all but the first row have a number of empty columns followed by a column with an X. The column with the X shows which is the column for the Notes data field for that password group, which is always the last data field in any password group. 

If you now e.g. want to enter pass word data for 20 web accounts, and 10 credit cards, then using the spreadsheet program, copy these rows so that you get 20 and 10 of these. Be sure not to insert any empty rows. Rows for other password groups not used can be kept as is.

When filling in data in the columns of a row, you can either see the meaning of the data to be put there in ch. 3, or you can go to the edit menu of the password group (New/Edit) to see it, and then do Delete without filling it out.

When you have created all the entries you want in the spreadsheet, save it as a CSV file, and quit the spreadsheet program. You may now just move this file back to the app directory in the phone, and go to the Database management menu, where you push the Batch input button. As there now is a file with the name PS_BatchInputData.csv in the directory, an empty template file will not be generated this time, but the content of the file will be read into the database. If the parser finds any errors in the data, you will get an error message, and then you must correct this on the PC, and redo. In that case it may be worthwhile visiting the UBVASA website where more information about batch input can be found.

After the file has been read into the database you will be asked if you want to encrypt the file. This may be a good idea as you then can move the encrypted file to the PC, and keep it securely there as a backup. If you answer yes, the internal file encryption menu will be opened, with the file name already filled in. You need to enter a password for the encryption (manually, or using the automatic generation), and push Encrypt file. You will then be asked if you want to remove the original (unencrypted) file, which probably is a good idea, and then finally push Done to take you back to the Select service menu, from which you can start to check the data stored in the database if you so wish.

As PS-Lite has a restriction on maximum 5 entries per password group, it may be not all data in the file is transferred to the database. 

Chapter 3 Password groups

After logging in, the first menu shown is one in which you can select which password group to access (also the database management services discussed in chapter 2 is shown here). Klicking on the spinner presents the groups discussed in the subchapters 3.x below. After selecting one of them you push the go button, which then presents a menu from which you can select between the following activities for the selected password group: * Create a new entry - select New on the spinner, and push Edit. * Edit an existing entry - select the entry on the spinner, and push Edit * View an existing entry - select the entry on the spinner, and push View You can also search for an entry by long pushing on the spinner. A dialog then opens in which you can enter a string of characters, then push Done. All the entries for this password group in the database will then be searched for a match with the entered string, and the first match found will be set as the spinner selection (so you do not have to enter the complete name, just enough to make it a unique match). This functionality is probably more useful when using PasswordServant where there is no restriction on the number of entries. The menus shown after pushing either Edit or View contains the same information (the View menu contains an additional Date field showing when the entry was last edited). However, in the View menu it is not possible to change any of the data. Therefore it is recommended to use this menu when there is no intention of changing any data, in order to prevent any misintentional modifications. A misintentional change of the password will most likely lead to problems! Some fields are in the View menu shown as if they could be edited. The reason for this is that showing them like that enables the possibility to use the Android generic copy/paste functionality. By long pushing on the field, a dialog opens with a few different choices. Push on "Select all" (which makes the field "selected"), and then again long push on the now selected field opens a new dialog in which you can select "Copy". Now the data in the field is copied into Androids copy/paste buffer, so you can now start any other application, and in that application long push on any field in which text can be entered, and then select "Paste" in the dialog that opens, which then leads to that the data field from PS-Lite gets copied there in. You can jump back and forth between the two apps by using the Adroid Home button. In the edit menu there are also buttons for generating a random password (se ch. 4), and for deleting the current entry from the database. This general structure is common for all the different password groups, the difference between them are what fields they contain, as described in the following subchapters.

Chapter 3.1 Web account

This password group is meant to be used for storing password information related to logins on the web. It contains the following fields: - Name: This is what is shown in the spinner, representing this entry. It should be unique, informative, and short (max 35 chars) - URL: the web address to the site where you want to login (max 150 chars). - User name: The user name to be used for logging in (max 35 chars). - Password: The password for logging in (max 35 chars). - Date of edit: The date for the latest editing of any field in this entry. This field is only shown in the View menu, and can not be edited by the user. - Notes: A field for writing extra information related to this entry (max 160 chars). The fields for URL, user name, and password can in the View menu be copied as described above, and then copied e.g. into suitable fields in the browser app.

Chapter 3.2 Computer login

This password group is meant to be used for storing password information related to computer logins. It contains the following fields: - Name: This is what is shown in the spinner, representing this entry. It should be unique, informative, and short (max 35 chars) - User name: The user name to be used for logging in (max 35 chars). - Password: The password for logging in (max 35 chars). - Date of edit: The date for the latest editing of any field in this entry. This field is only shown in the View menu, and can not be edited by the user. - Notes: A field for writing extra information related to this entry (max 160 chars). The fields for user name, and password can in the View menu be copied as described above, and then copied e.g. into suitable fields in an app for remote computer access.

Chapter 3.3 Credit card

This password group is meant to be used for storing password information related to credit cards. It contains the following fields: - Name: This is what is shown in the spinner, representing this entry. It should be unique, informative, and short. (max 35 chars) - Owner name: The name on the credit card (max 35 chars). - Number: The number on the credit card (max 16 chars). - Validity date: The date on the credit card telling how long it is valid. Format "mm-yy" (max 5 chars). - Security code: The The three digits on the back of the card (max 3 chars). - Password: The password for logging in (max 35 chars). - Date of edit: The date for the latest editing of any field in this entry. This field is only shown in the View menu, and can not be edited by the user. - Notes: A field for writing extra information related to this entry (max 160 chars). The fields for owner name, number, and password can in the View menu be copied as described above, and then copied e.g. into suitable fields in another app.

Chapter 3.4 Mail account

This password group is meant to be used for storing password information related to mail accounts. It contains the following fields: - Name: This is what is shown in the spinner, representing this entry. It should be unique, informative, and short (max 35 chars) - User name: The user name to be used for logging in (max 35 chars). - Password: The password for logging in (max 35 chars). - Date of edit: The date for the latest editing of any field in this entry. This field is only shown in the View menu, and can not be edited by the user. - Notes: A field for writing extra information related to this entry (max 160 chars). The fields for user name, and password can in the View menu be copied as described above, and then copied e.g. into suitable fields in another app. Information about the mail server URL, and settings, can preferrably be entered into the Notes field.

Chapter 3.5 Gate code

This password group is meant to be used for storing password information related to gate codes (lockers, etc). It contains the following fields: - Name: This is what is shown in the spinner, representing this entry. It should be unique, informative, and short (max 35 chars) - Password: The password for logging in (max 35 chars). - Date of edit: The date for the latest editing of any field in this entry. This field is only shown in the View menu, and can not be edited by the user. - Notes: A field for writing extra information related to this entry (max 160 chars). The field for password can in the View menu be copied as described above, and then copied e.g. into a suitable field in another app.

Chapter 3.6 Internal file encryption

This password group is meant to be used for storing password information related to files encrypted in the apps internal directory. It contains the following fields: - Original file name: This is what is shown in the spinner, representing this entry. It must be the exact name of the unencrypted file, also containing the file extension, i.e. presented as name.extension (max 35 chars) - Path to encrypted file: The path to where you will later keep the encrypted file. This field is informational only, for you to find the encrypted file, that needs to be moved back again to the apps internal directory if you want to decrypt it. (max 35 chars). - Password: The password for encrypting/decrypting the file (max 35 chars). - Date of edit: The date for the latest editing of any field in this entry. This field is only shown in the View menu, and can not be edited by the user. - Notes: A field for writing extra information related to this entry (max 160 chars). The file to be encrypted is moved to the app internal directory, for encryption you need to enter the edit menu. The file name with extension must be entered in the Original file name entry. After creating the password, push "Encrypt file" and a new file is created in the internal directory, having the name of the the original file, but with the file extension "psenc". This is the encrypted version of the original file (still existing in the directory). Now you can move the encrypted file to wherever you want to save it, e.g. to an external PC. Please remember to take care of the unecrypted file also (e.g. delete it). When you want to decrypt an earlier encrypted file, move it to the internal directory, open the entry in the View menu for this file in the app, and push "Decrypt file". The file is then decrypted and stored in the internal directory, with the file name and extension as in the Original file name field. The encrypted file is also kept in this directory. Both files can be moved, or handled as you wish.

Chapter 3.7 External file encryption

This password group is meant to be used for storing password information related to files encrypted on any other device than this phone (e.g. on a PC). It contains the following fields: - Original file name: This is what is shown in the spinner, representing this entry. It is a good idea to show the exact name of the unencrypted file, also containing the file extension, i.e. presented as name.extension (max 35 chars) - Path to encrypted file: The path to where you will keep the encrypted file. This field is informational only, for you to find the encrypted file, that needs to be moved back again to the apps internal directory if you want to decrypt it. (max 35 chars). - Encryption tool: The tool (i.e. program/app) used for encrypting/decrypting the file (max 35 chars). - Password: The password for encrypting/decrypting the file (max 35 chars). - Date of edit: The date for the latest editing of any field in this entry. This field is only shown in the View menu, and can not be edited by the user. - Notes: A field for writing extra information related to this entry (max 160 chars). The fields for path to encrypted file, and password can in the View menu be copied as described above, and then copied e.g. into suitable fields in another app.

Chapter 3.8 Network login

This password group is meant to be used for storing password information related to login on wireless networks. It contains the following fields: - Network name: This is what is shown in the spinner, representing this entry. It is a good idea to show the name that is shown in network manager, or a short of it (max 35 chars) - Service Set Identifier (SSID): This is the exact name that the network manager presents. (max 35 chars). - Security type: This shows the type of security solution that protects the wireless network. It is typically either WEP/WPA/WPA2. For the two latter it may have the postfix PSK. (max 35 chars). - Crypto type: This could be akronyms like tkip/EAP/LEAP etc, and has to do with the authentication method used. - Password: The password needed to login (max 35 chars) - Date of edit: The date for the latest editing of any field in this entry. This field is only shown in the View menu, and can not be edited by the user. - Notes: A field for writing extra information related to this entry (max 160 chars).

Chapter 3.9 Userdefined password groups

In Password Servant (not supported in PS-Lite) it is possible to define your own templates for what fields (and their field names) a password group shall contain. By selecting User defined groups on the spinner, and then New, you are taken to a menu where you are first asked about the Group name. Here you enter the name you want to associate to all entries in this group (1-35 chars). It is wise to give it a unique name, relating to the nature of the data that it will hold. Next you are asked about an Entry name, the text that will be shown above the first field of the template (the name field). You can make it as simple as Name if you wish. The data entered in the field associated to this text (when you later will use this template to enter data) is what will be shown in the spinner showing all existing entries, and this filed is not encrypted in the database. After being done with this you will be in a menu with eight rows, each row having two fields for data entry. The leftmost field, called Field name X (2<=X<=8) is where you enter the name that you want to be associated with a data entry field, and the right most, called Field size X, is how many characters you max want to allow as input for this data field (1-175). You can now fill in the number of rows you want in your template, from zero to all eight rows. When done with this you push the Done button. This will lead to a pop up window saying Link passowrd property to field, and showing a spinner with the option No link shown. If you open the spinner you will, besides the No link option, see the names of the fields you have defined. You can now choose if you want one of these fields to be defined as a password field, meaning that the Generate password button in the Edit menu will be linked to this field. If you choose No link this button will not be shown at all in the Edit menu (so passwords then have to be generated by yourself if you need any). After making this selection you are done with the password group definition, and taken back to the earlier menu. Now you can find and select your new password group on the spinner, which then takes you to the menu where you can choose between generating a new entry, or view or edit an existing entry. If you at some point want to completely remove the password group you have defined, then you need to remove all entries on it one by one (by pushing Delete in the Edit menu). When you have deleted the last one you get a question if you want to delete the group definition. Answering yes will then remove the complete group definition from the database. When you have defined any own password groups, these will automatically be included in the batch input template, in the case you generate such a file (c.f. ch. 4.3). So batch input will work for your own defined groups also. A short summary of the user defined password group service: - A user defined password group must have a group name (which should be unique) - The first row (mandatory) is the entry name row, which is what is shown in the spinner. Its data is saved unencrypted in the database. The name of the row (shown in the Edit/View menus) are user defined. - Zero to seven rows may be defined to follow the name row. The name of the rows (shown in the Edit/View menus) are user defined. By defining a name in the group definition menu, the row will be added to the template (leaving the row empty leads to its removal from the template). The max number of characters that can be entered is also defined. - One of the max seven rows can be defined as a password row, which will then link the automatical password generation service to that row. - A user defined password group can be deleted after removing the last entry in the group. - Batch input supports user defined groups.

Chapter 4 Use cases

Chapter 4.1 Password generation

If you do not want to come up with a password yourself you can push the button "Generate password" when in the Edit menu of any password group. This takes you to a menu in which you can select the number of characters that you want the password to have ([1..35] chars), and the "scope" for the characters used in this random generation. The scope can be one of the following: - Numberic: The digits zero through nine: [0..9]. - Alphanumeric: Numberic plus the alphabet in lower plus upper case: [0..9] + [a..z] + [A..Z] - Alphanumeric extended: Alphanumeric plus special characters: [0..9] + [a..z] + [A..Z] + [!#%&/()+;:,.=?-_<>]. The selected scope is shown with a slightly larger font than the others. Pushing "Set scope" opens a dialog in which one of the three scope settings can be selected. This selection is the used in the following (and shown with a slightly larger font). You are of course free to modify the result of the random password generation if you are not satisfied with the result, or redo it until you are.

Chapter 4.2 Secure sharing of files

A file that has been encrypted using the internal file encryption does not necessarily be decrypted on the same device. The en crypted file can be sent to any other Android device running PasswordServant or PS-Lite, and if you share the password (in a secure way) with the user of that device, then the file can be decrypted there. To decrypt the file on a device where it has not been encrypted, the file must as usual be stored in the apps internal directory, then a new entry must be edited in the internal file encryption password group. In this entry it is important to write in the original file name field the exact file name of the file to be decrypted, but it should not be given the file extension of the encrypted file (psenc), instead it should be given the proper file extension that matches the file when unencrypted (if not known, ask the person who provided you the file). Also the password must be written into its field, then you push "Done" to save the entry, and leave the edit menu. Now, open the same entry in View mode, and there push "Decrypt", and the decrypted file will appear in the app internal directory with the name and extension as shown in the original file name field. so this way you can share files over e.g. Internet in a secure way with your friends, family, etc. It is however important that you select a secure way to send the password. Using SMS is considered relatively secure, regular mail PC to PC is not considered secure.

Chapter 4.3 Optional password

This feature is not supported in the free version PS-Lite. After reading the article 'Secure Password Managers and Military-Grade Encryption on Smartphones: Oh, Really?' (http://www.elcomsoft.com/WP/BH-EU-2012-WP.pdf) I realised that for really skillful and resourceful organisations it is within reach to crack even well designed password managers in a reasonable time. In this article it is stated that this company, using their full talent and resources as a security company, could crack evenn the best designed apps in about one day, given that the passwords were around 10 characters long. The worst ones were cracked in seconds, or less. So even if my app the Password Servant followed the design rules for withstanding one day of expert level cracking, the article got me to believe this is not enough. Therefore I invented the 'Optional password', a second password. The idea here is that this password shall be a truly 'random' password, i. e. not a reckognizable word or similar. This password, which is only four characters, you will probably have to have written on a piece of paper stored in your wallet. At least for quite some time until you eventually learn it. Having this written on a piece of paper is of course a sort of security risk. But what is very important is that you do not have the primary password also on a piece of paper in you wallet. Then, even if both your phone and your wallet is stolen, the password database is still protected by the primary password. And very few crackers are as skillful as ElcomSoft, so it might still be enough. Adding this Optional password, and provided you select a truly 'random' password for it, will increase the computational cracking effort about 52 million times. So instead of one day, it would take 143 thousand years! That should deter most thieves. To support you in selecting a random password I have added the button 'Generate optional password' which you can push any number of times until it creates a random password that looks good to you. You can also edit 'by hand', writing whatever characters you like. You should write these four characters down directly, or else it is likely that you do not remember them next time. As the name indicates this is an optional password, and you can leave it blank if you wish. But then you should make your primary password considerably longer than 10 characters, or at least have it contain some unusual characters. With this addition I am pretty sure that the Password Servant is best in class among the Android apps when it comes to cracking robustness.

Chapter 4.4 Inactivity timeout

If you forget to close the Password Servant application after you are done with it, there is an inactivity timeout that will auto-lock the app one minute after one of the following two events - a) one minute after the application loses focus (i. e. it is no longer the active application, b) one minute after the screen is inactivated ("goes black"). The auto-locking leads to that next time the app gets in focus the login menu is displayed, and you have to enter the password again. The user selection is also locked to the user that was active at the time of auto-locking. Once the correct password is entered, the menu that was displayed before the auto-locking is again displayed, in the state that it was left in. This takes care of the scenario where you loose your phone with Password Servant still running. If a potential thief does not get hold of it before the one minute timeout has expired, then it is not possible to access any data without first entering the password (incl. the optional password, if used).

Chapter 5 END-USER LICENSE AGREEMENT FOR Password Servant and/or PS-Lite

IMPORTANT PLEASE READ THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT CAREFULLY BEFORE CONTINUING WITH THIS PROGRAM INSTALL: UBVASA End-User License Agreement ("EULA") is a legal agreement between you (either an individual or a single entity) and UBVASA. for the UBVASA software product(s) identified above which may include associated software components, media, printed materials, and "online" or electronic documentation ("SOFTWARE PRODUCT"). By installing, copying, or otherwise using the SOFTWARE PRODUCT, you agree to be bound by the terms of this EULA. This license agreement represents the entire agreement concerning the program between you and UBVASA, (referred to as "licenser"), and it supersedes any prior proposal, representation, or understanding between the parties. If you do not agree to the terms of this EULA, do not install or use the SOFTWARE PRODUCT.

The SOFTWARE PRODUCT is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE PRODUCT is licensed, not sold.

5.1. GRANT OF LICENSE. The SOFTWARE PRODUCT is licensed as follows: (a) Installation and Use. UBVASA grants you the right to install and use copies of the SOFTWARE PRODUCT on your device.

5.2. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS. (a) Maintenance of Copyright Notices. You must not remove or alter any copyright notices on any and all copies of the SOFTWARE PRODUCT. (b) Distribution. You may not distribute registered copies of the SOFTWARE PRODUCT to third parties. Evaluation versions available for download from UBVASA"s websites may be freely distributed. (c) Prohibition on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer, decompile, or disassemble the SOFTWARE PRODUCT, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation. (d) Rental. You may not rent, lease, or lend the SOFTWARE PRODUCT. (e) Support Services. No support is provided (f) Compliance with Applicable Laws. You must comply with all applicable laws regarding use of the SOFTWARE PRODUCT.

5.3. TERMINATION Without prejudice to any other rights, UBVASA may terminate this EULA if you fail to comply with the terms and conditions of this EULA. In such event, you must destroy all copies of the SOFTWARE PRODUCT in your possession.

5.4. COPYRIGHT All title, including but not limited to copyrights, in and to the SOFTWARE PRODUCT and any copies thereof are owned by UBVASA or its suppliers. All title and intellectual property rights in and to the content which may be accessed through use of the SOFTWARE PRODUCT is the property of the respective content owner and may be protected by applicable copyright or other intellectual property laws and treaties. This EULA grants you no rights to use such content. All rights not expressly granted are reserved by UBVASA.

5.5. NO WARRANTIES UBVASA expressly disclaims any warranty for the SOFTWARE PRODUCT. The SOFTWARE PRODUCT is provided "As Is" without any express or implied warranty of any kind, including but not limited to any warranties of merchantability, noninfringement, or fitness of a particular purpose. UBVASA does not warrant or assume responsibility for the accuracy or completeness of any information, text, graphics, links or other items contained within the SOFTWARE PRODUCT. UBVASA makes no warranties respecting any harm that may be caused by the transmission of a computer virus, worm, time bomb, logic bomb, or other such computer program. UBVASA further expressly disclaims any warranty or representation to Authorized Users or to any third party.

5.6. LIMITATION OF LIABILITY In no event shall UBVASA be liable for any damages (including, without limitation, lost profits, business interruption, or lost information) rising out of "Authorized Users" use of or inability to use the SOFTWARE PRODUCT, even if UBVASA has been advised of the possibility of such damages. In no event will UBVASA be liable for loss of data or for indirect, special, incidental, consequential (including lost profit), or other damages based in contract, tort or otherwise. UBVASA shall have no liability with respect to the content of the SOFTWARE PRODUCT or any part thereof, including but not limited to errors or omissions contained therein, libel, infringements of rights of publicity, privacy, trademark rights, business interruption, personal injury, loss of privacy, moral rights or the disclosure of confidential information.

(*) The beginning of the sdcard path ("/mnt/sdcard/...") may vary on different devices. Shown here is how it looks on my phone. The rest of the path should however be as shown.

You can read this help information for Password Servant/PS-Lite on a larger screen if surfing to the UBVASA homepage: https://sites.google.com/site/ubvasa/

I hope Password Servant/PS-Lite will help you to securely handle all your passwords!