A Variety of Uses
Crosspass can be used for a variety of purposes to improve the privacy and security of communication.
Sending a Password
The most obvious case for Crosspass is the sending of a password. Suppose Alice works for company Acme Inc. and she needs to email login credentials to a business client Bob. Usually in such business setting email is the method of communication of choice.
- Alice opens Crosspass app and creates a password share.
- Takes note of the Lookup ID and PIN.
- Composes the email as per usual, but instead of the password puts the Lookup ID and PIN for Crosspass.
Thank you for signing up with Acme!
We have now created an account for you.
Password: Crosspass AXYZ 2475
Note: For your privacy I am sending you the password using the Crosspass app.
Please install it on your phone and retrieve the password using information above.
Sending an API key
Often IT businesses allow access to an API using an auth key which is unique for every client. Alice can send the API key the same way she would send a password. For example:
Thank you for signing up with Acme! We have now created an API key for you.
Use the Crosspass app to retrieve the key securely,
Lookup ID: AXYZ
Note: You will need to install Crosspass on your phone.
Sending a Bank Account Number
Suppose Alice wants Bob to wire her money. She uses Crosspass to create a shared note with the following information:
Beneficiary name: Alice Doe Bank account number: 439587382957 Beneficiary address: 123 Broadway St, Apt 1, Gotham City
Then she sends Lookup ID and PIN to Bob by email or IM.
Sending a Credit Card Number
Suppose Alice wants Bob to charge her credit card . She uses Crosspass to create a shared note with the following information:
Name on card: Alice Doe Credit card number: 1111 2222 3333 4444 Expiry: 01/28 CVV: 123 Billing Zip code: 12345
Then she sends Lookup ID to Bob by email or IM and asks him to install the Crosspass app. When Bob asks her for the PIN, she calls him to give him the PIN. Bob then immediately retrieves the credit card number.
Sending a Social Security Number
It is well known that Social Security numbers (in USA) and Social Insurance numbers (in Canada) are regarded as highly private. Let’s say Alice wants to send Bob her Social Security number. She would use Crosspass to create a shared note with her Social Security number and email the Lookup ID and PIN to Bob.
Sending a Microsoft Word file
Suppose Alice has a private document that she wishes to share with Bob.
- Alice chooses a strong password and stores it somewhere
- She installs the 7-zip app on or her PC or Mac
- She creates a new folder
ForBoband places the Microsoft Word file into the folder
- She creates a
ForBob.zipfile using 7-zip, selecting AES encryption with the chosen password
- She sends the file
ForBob.zipto Bob by email, Dropbox, or Google Drive
- She opens Crosspass app and creates a password share with the chosen password
- She notes the Lookup ID and PIN and sends them to Bob by email or IM
On the receiving end Bob does not need to install 7-zip. The received ZIP file can be decompressed in Mac and Windows, since they natively support AES decryption. Bob receives the password using Crosspass and decrypts the
Verifying WhatsApp Encryption
Alice wants to make sure that her conversation with Bob is end-to-end encrypted.
- She uses WhatsApp app to view Bob’s profile.
- In Bob’s profile she selects Security Code in order to view a 60 digits long number.
- She uses Crosspass to create a shared note with these 60 digits.
- She receives the Lookup ID and PIN for this note.
- She texts the Lookup ID to Bob by WhatsApp and asks him to install Crosspass.
- She calls Bob on the phone and tells him the PIN.
Bob then uses the Lookup ID and PIN to retrieve the Security Code. He opens Alice’s profile in WhatsApp, then views her Security Code in the profile and verifies that it is the same as what he received by Crosspass.
Verifying Signal Encryption
Same as WhatsApp, except in Signal the “Security Code” is called “Safety Numbers.”
Sending a Bitcoin Address Anonymously
Cryptocurrencies like ZCash and Monero go to great complications in the protocol in order to hide the identity of the address owner. Other cryptocurrencies, including Bitcoin, do not have this anonymity feature.
However, this level of anonymity can be achieved with Crosspass easily for any cryptocurrency. Let’s say Alice wants to send to Bob her Bitcoin address, but she does not want anyone else except Bob to know that this address is hers.
- Alice uses Crosspass to create a note share with the Bitcoin address as the value
- She sends the Lookup ID and PIN to Bob by email or IM
On the receiving end, Bob uses Crosspass to retrieve the Bitcoin address.
Collaborating using an Encrypted Cloud Drive
Let’s say Alice and Bob wish to share files on an end-to-end encrypted cloud drive.
- Alice creates a Google Drive folder and shares with Bob.
- Bob and Alice install Google Drive on their laptops (Mac or PC), and verify that they can place non-secret files into the shared folder.
- Alice chooses a strong password and stores it somewhere.
- She installs Cryptomator app on her laptop and creates a Cryptomator Vault in the shared Google Drive folder.
- When Cryptomator asks her to choose a password, she uses the password which she has created.
- She uses Crosspass to create a password share with the chosen password as the value.
- She receives Lookup ID and PIN from Crosspass.
- She sends the Lookup ID and PIN to Bob by IM or email.
On the receiving end Bob uses Crosspass to retrieve the shared password. He installs Cryptomator on his laptop and tries to unlock the Cryptomator Vault. When Cryptomator asks him for the password, he uses the password that he has received.
Sending an Encryption Key
An symmetric encryption key is just a long password. Therefore, Alice would send it by Crosspass the same way as she would send a password.
Verifying a Digitally Signed PDF
Alice uses Adobe to digitally sign a PDF and emails it to Bob. Bob does not trust the Adobe verification, and wants to independently verify the signature. This can be verified by comparing the Fingerprint value of the signing certificate. The Fingerprint value is a long string of letters and digits that can be found in certificate details.
- Bob asks Alice to send him the Fingerprint of her signing certificate.
- She opens the details of her certificate to view the Fingerprint value
- Alice uses Crosspass to create a shared note with and copy-pastes the long Fingerprint into it
- She receives a Lookup ID and PIN for the note from Crosspass
- She sends the Lookup ID and PIN to Bob
On the receiving end Bob uses the Lookup ID and PIN to receive the Fingerprint. He uses Adobe to view the detail of the signing certificate. The details show the Fingerprint value. He compares that the received Fingerprint value is the same.
Verifying a PGP key
Pretty Good Privacy (PGP) is a standard to encrypt email. Bob wants to send an encrypted email to Alice, and he needs her PGP key. When Alice creates her PGP key, the public part of the key is automatically uploaded to a public PGP server and is listed under her email address.
- Bob’s software downloads Alice’s PGP key from a public PGP key server.
- Bob asks Alice to send him the Fingerprint of her PGP key.
- Alice uses her PGP software to view the Fingerprint of her PGP key.
- Alice creates a shared Crosspass note with the Fingerprint.
- She receives Lookup ID and PIN from Crosspass.
- She emails the Lookup ID to Bob, and calls Bob to tell him the PIN.
- Bob uses the Lookup ID and PIN to retrieve the Fingerprint.