KisKis provides some basic account types for different purposes, such as “Network Accounts”, “Bank Accounts”, “Secured Files” and “Credit Cards”. However, if the attributes of them doesn't meet your needs, you can define your own account types in an easy way.
This is the most often used account type. It can be used for computer-logins, mailserver-authentications, internet services and so on.
The network account provides additional attributes for:
username: Typical use is the login name of an internet service or computer account.
URL: The location where the service or computer can be found. This URL can be delivered to the Build-In-Application-Starter, so that you can associate your preferred application to it. Therefore, you would have to click on the button “open URL”. Examples: http://www.foo.de/?un=%username&pwd=%pwd or pop://mail.foo.de/
eMail: If anybody wanted to know an email address you can type it in here. This is very useful if you have multiple email accounts and if you want to keep track which account knows which email address, especially if you use such services like spamgourmet.com.
This account type models a typical money account on a bank. It provides some additional attributes needed for financial transactions such as “telephone-pin”, “account number”, ...
Notice the TAN-list field for Transaction-Numbers. It is used to define sets of TANs. Each TAN-list is identified by an ID and a creation date. Within the following dialog the TANs can be added, removed or marked as used.
A “Credit Card” is usually associated with a bank and has a tiny pin. Though, the most interesting part is its number which can be entered as well.
You can check your password quality with two internal tools. The first is a simple analyzer which tests the strength of your password depending on the character set used. A character set describes numbers, lower-case letters, upper-case letters, punctuation, ... The more different character sets a password uses, the more secure it is because a brute force attack needs to take more possible variations into account.
The second way is a dictionary-based check using cracklib. The password is validated against a dictionary. If cracklib is able to find parts of the word in its dictionary you should use another password because a dictionary-based attack on your account could succeed with a high probability.
You can use your own wordlist as dictionary. Create a simple text-file with a word for each line. The words have to be sorted alphabetically.
Example:
aron
berta
# a comment will be ignored
julia
zoron
Once you created this file you can create a cracklib-dict. Just open “Edit/Options/Cracklib Dictionary”
The default should look as in the picture above.
Enter a new name in “Cracklib Dictionary filename”, e. g. mydict.
Click the button for “create new Dictionary from wordlist” and select your wordlist file.
A new dictionary mydict.pwd will be created.
Click on save.
You can use an existing cracklib-dictionary as well. Just click on “select an existing dictionary file” and select the “*.pwd”-file.
Open the menu item “Edit/Manage account templates” to open the template overview dialog.
Here you can see all your defined account templates. In this case, two were already defined. Note that an item is unqiuely identified by its name (case-sensitive). So you cannot have a second item called “My Credit Card”. All the templates are stored within your current datafile.
Just click on the “new”-button. A new item called “new template” will appear.
Double-click on the item of your choice to open the “template editor dialog”.
Name your template and add some tiny properties with “new” and “edit” to it. You can order them using the arrow buttons on the right panel.
Give each property a unqiue name within the template and chose a type out of the combo-box. As you can see, the following types are supported:
Date: will be rendered as a date field.
Password: will be rendered as a password field.
String: will be rendered as a simple text field.
URL: will be rendered as a URL-input field which allows you to start an associated application.
TODO: RichText: will be rendered as a text area.
Warning:
Be careful when modifying a template you have already instanciated and filled with important data. New properties aren't a problem at all. But keep in mind, that deleting a property will delete ALL associated values from the instances as well. You should also note that deleting a template will delete all instances.
Just click on “delete” to remove the selected item. If the item is currently instanciated a warning will be shown.
KisKis provides a basic feature to import existent data via “comma-separated-values”-files. Just activate the menu item “File/import” to start the procedure. Note that the imported accounts will be typed as “Network Accounts” and will be added to the opened file.
The CSV-file should be formatted as follows:
A header with pre-defined values must be included:
group
label
password
username
email
url
created (a date formatted as: YYYY-MM-DD)
expiration (a date formatted as: YYYY-MM-DD)
comment
at least one row should exist
group | label | password | username | email | url | created
My Group | My Account Name | My Secret Password | MyUsername | foo@bar | http://localhost:8080/foo | 2004-01-01
My Group | Second | secret ||||
Notice the header in the first line and two different data rows. The order in the column header is not important.
You don't have to provide values for each column. You could use the header
label | password
as well and omit the other column values ( the rest will be filled with pre-defined standard values). But if you have defined two columns in the header, each data row MUST provide two columns as well (but a column can be empty). If you don't provide a group-column the root-node will receive the new account.
In this example the field-delimiter is '|'. You can chose any other character sequence, but be sure, that this sequence cannot be found within your data-values! Leading and trailing spaces within each field will be cut and ignored.
An import-action cannot be made undone.
To retrieve the specified format You can use existing office-applications like OpenOffice Calc or Microsoft Excel.
Just open the existing ASCII-file as a CSV-file, rename the columns, reformat the values if needed and save it back again as a CSV-file.
It might happen, that the office-application uses the '”'-character as a text-marker. In this case, You can remove them with a simple text-editor (VI, Notepad, ...) using the search-and-replace-function.
“Network Accounts” provide the facility to open an URL with an external program. The prefix of the URL will be matched with a list of defined prefixes for external programs.
Therefore you have perform the following steps:
Register an application
Open the menu item “Help/Options”
Select the tab “Applications”
Create a new entry in the ordered list. This list is processed from top. The first matching entry is executed. So you have to enter the more specific prefixes at first, the more general at last.
Enter the command line that will start the program. Make sure, that the executable can be found by KisKis. A variable named “%url” can be placed within the command line. This variable will be substituted with an concrete URL when running the program.
Enter an URL-prefix for this entry.
Save the changes.
Enter an URL in a new “Network Account”
Create a new “Network Account” by “edit/new account/Network Account”.
Enter a password, username, email and URL in the specific fields.
The URL can contain some extra variables which will be substituted like:
%username
%pwd
%email
Apply the changes.
Push the button “Open URL”. The external program should now be opened.
1:http://localhost => c:\opera\opera.exe %url
2:http => d:\firefox\firefox.exe -remote "openURL(
%url, new-tab)”
3:=> explorer.exe %url
1:http://localhost => /opt/opera/opera %url
2:http => /opt/firefox/firefox -remote "openURL(
%url, new-tab)”
3:=> kfmclient exec %url
As you can see, all Web-Sites on your local machine will be opened by Opera (line 1), the rest is viewed using Firefox (2). Line 3 will be used for all URL's which begin with anything but http.
Normally you should not be bothered with the manual decryption of attachments, but here is how it works:
File attachments are stored as separate files which are associated with the password-file (e. g. kiskis.xml) by name for efficiency reasons. All attachments of kiskis.xml can be found as kiskis.xml.attachment.<i> encrypted as separate PGP-Messages. Each attachment is encrypted with a new random key which you can find within the kiskis.xml-file in the <Attachment>-element.