Index
Overview
Navigation and Tool Bars
Send a Vault
Send a Lock
Main Screen -> ->
Main Screen -> ->
Main Screen -> -> -> Document Options (Tap on Lock) -> Send Lock
Overview   top
With this screen you can send a lock or a vault to someone else. In order to receive vaults from someone else you must send them a lock.

You can send documents securely to another person by creating a vault. Since a vault encrypts its contents for someone else, the recipient of the vault must have sent you a lock. You pick a recipient's lock from a list, enter text and/or add documents to the two compartments of the vault, and then create it and send it. Optionally you can digitally sign the vault so the recipient knows it comes from you and has not been tampered with.

Navigation and Tool Bars   top
: you will be asked to send your vault or lock. Prepared vaults will be discarded if you choose not to send.

Send a Vault   top
Advanced Settings: switch this on or off to show or hide some of the less-used settings. Switch it off to make the screen a bit less overwhelming.

Recipient: tap to pick the recipient's lock. Received locks usually contain the (public) encryption keys as well as the contact information of the recipient. If necessary, you can change or enter the contact address just before you send the vault. Choose one of your own locks to send the vault to yourself.

Size of Added Junk Data: you can specify an amount of junk data to be added to the vault. This will make it difficult for an attacker to glean any information about the content of the vault based on its file size. Since a vault contains two compartments this also conceals any size differences in the contents of the compartments.

For example, if you have small (or no) coercion data and a large image as the normal data, adding junk data will help hide the fact that you opened the coercion compartment - its small data size compared to the overall size of the vault may only indicate a large amount of junk data, not that there is more data in the normal compartment.

Vault (): tap to compose the data in the two vault compartments. When you are done, the vault will be created by encrypting the data with the recipient's lock. (Which means that whenever you change the recipient, the vault data will be deleted - it is the recipient's data.)

You can add locked documents to the vault - they will be indicated with an orange lock. However, in all likelihood the recipient won't be able to open them. To avoid this, tap on the orange lock to unlock the documents or remove them from the vault.

Include Sender Info: switch this on to include your image, name and contact addresses in the vault. You will see your image overlaid on the vault icon which is also how it will appear in the recipient's document list.

Signature: tap to authenticate with your signature lock (or data or log in lock). This adds a special string to the vault which will let the recipient check that the vault is indeed from you and that it has not been tampered with. If you are under duress, you can use the coercion functionality to signal this to the recipient. However, if they are under duress when opening the vault, this will reveal that you signalled and also that you have a coercion item.

To verify your digital signature the recipient will previously have to have received a lock from you. When they open the vault, a special document will be created showing the result of the verification. This document will show your signature (if your identity has one), your image, a check number and the time and date of your signature.
See Security Features: Digital Signatures for more details.

Send in Container: you can choose to hide the vault inside a container image. (See Data Formats: Containers and Terminology and Concepts: Steganography.) This will make your vault appear as an innocuous image (well, as long as the image is innocuous). Note: you must send the image in Actual Size or you will destroy the vault!

Choose Container: tap to choose an image to use as a container. Otherwise, the default container specified in the current identity is used.

Container Quality: the higher the quality of the resulting image, the less data can be hidden in each byte; therefore the image must be bigger. For e-mails and SMS this can make the difference between being able to send or not.

Send a Lock   top
In order to receive vaults from someone else you must send them a lock. What will be sent are the public keys they can use to encrypt information which only you can decipher. Your access sequences and private keys will not be sent. The lock will, however, include your contact information (image, name, contact addresses). This information will show up in the recipient's list of locks and will be used to fill in the destination address when they send you a vault.

Lock: choose the lock you wish to send if it's not already filled in.

Recipient Image and Name: you can set an image and/or name for the recipient if it has not been entered from your address book. Tap to choose from your address book; tap to pick an image from your document list. This information will help you identify the lock in your own 'Sent Locks' list. Swipe across the row and 'Clear' the information if you don't want it stored in the lock.

Recipient E-mail Address:
Recipient SMS Number:
SDX Upload Server:
tap to enter the recipient's address for each mode of transmission. You can also pick the addresses from your address book (). The SDX Upload Server can be a server provided by you or the recipient. It will be the server the recipient uploads data to and you will download data from. See Secure Data Exchange (SDX): Using a Server to Exchange Data for details. Note that the lock itself cannot be uploaded to a server since the recipient won't have a way to download it (you are sending him or her the server address with the lock).

Send in Container: you can choose to hide the lock inside a container image. (See Data Formats: Containers and Terminology and Concepts: Steganography.) This will make your lock appear as an innocuous image.

Choose Container: tap to choose an image to use as a container. Otherwise, the default container specified in the current identity is used.

Container Quality: the higher the quality of the resulting image, the less data can be hidden in each byte; therefore the image must be bigger. Locks to be sent are not large, so even the best quality will result in an image of less than 1MB in size.

Previous: Secure Communications (SMX)  Next: Vault Data
Copyright ©2014
bitSplit™ Enterprises.
All rights reserved.
Monday, January 6, 2014